Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d5a031bf832ccb401190c37a70aa3b8c8a7dbc9ab748e9c00e598487a0ddb28

Tx prefix hash: 21130ad8bd31e131cb3056d37b2c3eec2ff10e7d512dc5bc4786df7aa7f155ea
Tx public key: 1fa2ba1e8148a2dcc6855b9687744c39fea3bb7e991c35029a20c44d30207a5b
Timestamp: 1736458030 Timestamp [UCT]: 2025-01-09 21:27:10 Age [y:d:h:m:s]: 00:071:07:39:28
Block: 1193863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50745 RingCT/type: yes/0
Extra: 011fa2ba1e8148a2dcc6855b9687744c39fea3bb7e991c35029a20c44d30207a5b0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63d28e6acf0c2970802cf58da5c643e39f2377a66b7ee74b5a2e5ef0eaa7730a 0.600000000000 1680428 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": 1193873, "vin": [ { "gen": { "height": 1193863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63d28e6acf0c2970802cf58da5c643e39f2377a66b7ee74b5a2e5ef0eaa7730a" } } ], "extra": [ 1, 31, 162, 186, 30, 129, 72, 162, 220, 198, 133, 91, 150, 135, 116, 76, 57, 254, 163, 187, 126, 153, 28, 53, 2, 154, 32, 196, 77, 48, 32, 122, 91, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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