Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d869301802b07e4644f39a8f59af423ff6c8938389a0fcf96a75eeab88e7a148

Tx prefix hash: 76dfd77a08c8fd0306d40c0ea2f6f2f0f572f304e709dae33dca6ffbbe3d90bc
Tx public key: 506ebe3a4a333e0cf60afe950757b714e0963c792ec1fee65c4dd1011b66c727
Timestamp: 1727086400 Timestamp [UCT]: 2024-09-23 10:13:20 Age [y:d:h:m:s]: 00:062:12:51:02
Block: 1116303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44697 RingCT/type: yes/0
Extra: 01506ebe3a4a333e0cf60afe950757b714e0963c792ec1fee65c4dd1011b66c727021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0a1fb38f06f97d0b8e5a66cd40b018fe6123ca3379faa3169206b6e5f2e5d1f 0.600000000000 1596738 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": 1116313, "vin": [ { "gen": { "height": 1116303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0a1fb38f06f97d0b8e5a66cd40b018fe6123ca3379faa3169206b6e5f2e5d1f" } } ], "extra": [ 1, 80, 110, 190, 58, 74, 51, 62, 12, 246, 10, 254, 149, 7, 87, 183, 20, 224, 150, 60, 121, 46, 193, 254, 230, 92, 77, 209, 1, 27, 102, 199, 39, 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