Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 9b17994db9d1ceec6b8ac9731122cc24da3049e19c4b8de2e16842cbd76251de

Tx prefix hash: 3943d34b8aca6983634a5f78f4b934eaf0c2a0c9b8d3ce7a322b6df3b7094134
Tx public key: 36872b224956a4ebcd4313e8e47880f4e88d453a6405b24a1af1b36a03714dd8
Timestamp: 1719638006 Timestamp [UCT]: 2024-06-29 05:13:26 Age [y:d:h:m:s]: 00:293:01:44:05
Block: 1054549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209429 RingCT/type: yes/0
Extra: 0136872b224956a4ebcd4313e8e47880f4e88d453a6405b24a1af1b36a03714dd802110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a88c524c92fb0f4915248ea48346e4104ad53def18506e70cb49f99fe021dbc0 0.600000000000 1524912 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1054559, "vin": [ { "gen": { "height": 1054549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a88c524c92fb0f4915248ea48346e4104ad53def18506e70cb49f99fe021dbc0" } } ], "extra": [ 1, 54, 135, 43, 34, 73, 86, 164, 235, 205, 67, 19, 232, 228, 120, 128, 244, 232, 141, 69, 58, 100, 5, 178, 74, 26, 241, 179, 106, 3, 113, 77, 216, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8