Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9aa5192f2b7c08b3ac606a1f303e087c5b1bc44a54e0356547f84339a6c170ec

Tx prefix hash: 407a7472ad429942da71e80b280abb2fa4893aa746ee16c7cdb2742907956412
Tx public key: ef09f4c1cc37bca1167f7b807af2e3dd1954b458a7b1301dfaee630bb6d28842
Timestamp: 1723959582 Timestamp [UCT]: 2024-08-18 05:39:42 Age [y:d:h:m:s]: 01:140:18:32:29
Block: 1090390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359150 RingCT/type: yes/0
Extra: 01ef09f4c1cc37bca1167f7b807af2e3dd1954b458a7b1301dfaee630bb6d2884202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26db0ffac33b71e31f0c7ed829d2f0e1b313d944292446ca96b4c26fbbcc94e6 0.600000000000 1565013 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": 1090400, "vin": [ { "gen": { "height": 1090390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26db0ffac33b71e31f0c7ed829d2f0e1b313d944292446ca96b4c26fbbcc94e6" } } ], "extra": [ 1, 239, 9, 244, 193, 204, 55, 188, 161, 22, 127, 123, 128, 122, 242, 227, 221, 25, 84, 180, 88, 167, 177, 48, 29, 250, 238, 99, 11, 182, 210, 136, 66, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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