Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d72e35ac58de8b710b454ece21333aef4680c1b6a0b6a8cd067856537ca3d1a

Tx prefix hash: 90fff0a8044e5215efdcae1d351287608d97d849c1516aa60943ae8dea07d65b
Tx public key: 1e326e63cb8e60b20fd2ceb5ea715abe79554565e1f2279682fe340ded01e797
Timestamp: 1728911261 Timestamp [UCT]: 2024-10-14 13:07:41 Age [y:d:h:m:s]: 00:040:12:09:50
Block: 1131441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28910 RingCT/type: yes/0
Extra: 011e326e63cb8e60b20fd2ceb5ea715abe79554565e1f2279682fe340ded01e797021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 164094cbfbca4d4d91dc58c2cf2e3e7cd5a46d829009d4f49fd46d560e39b5c2 0.600000000000 1614342 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": 1131451, "vin": [ { "gen": { "height": 1131441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "164094cbfbca4d4d91dc58c2cf2e3e7cd5a46d829009d4f49fd46d560e39b5c2" } } ], "extra": [ 1, 30, 50, 110, 99, 203, 142, 96, 178, 15, 210, 206, 181, 234, 113, 90, 190, 121, 85, 69, 101, 225, 242, 39, 150, 130, 254, 52, 13, 237, 1, 231, 151, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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