Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ab257678c4358f72cc1fd95578f5322adb36c4412ba2cf53e650723ccf4cfb8

Tx prefix hash: da04c9fbb0fc98cab91b45c6bf31ce1adda43d7f0b022e4565da101cf5abedd4
Tx public key: 83f9198a9efe92a988d3a8ea876f7a06a603b44d6ad2bc10887e12d44b3e1505
Timestamp: 1721783613 Timestamp [UCT]: 2024-07-24 01:13:33 Age [y:d:h:m:s]: 00:169:04:26:31
Block: 1072339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121058 RingCT/type: yes/0
Extra: 0183f9198a9efe92a988d3a8ea876f7a06a603b44d6ad2bc10887e12d44b3e150502110000001be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0561b36cf504fa18f3d149e4182a9b894ba63770142751b132b65cde91ebd66 0.600000000000 1544802 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": 1072349, "vin": [ { "gen": { "height": 1072339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0561b36cf504fa18f3d149e4182a9b894ba63770142751b132b65cde91ebd66" } } ], "extra": [ 1, 131, 249, 25, 138, 158, 254, 146, 169, 136, 211, 168, 234, 135, 111, 122, 6, 166, 3, 180, 77, 106, 210, 188, 16, 136, 126, 18, 212, 75, 62, 21, 5, 2, 17, 0, 0, 0, 27, 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