Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c217fad8f5f6504439ebe66cf2e59c7214a0daf121f9f55bd17423cfa65e21d

Tx prefix hash: 76fb4dc47621c4b322f638262a39d0363dd8d5e469814e656019c178a493eca2
Tx public key: 4e134d171561f442c79f7b87407301e523540e1a7ce563c809d9997a00b08093
Timestamp: 1762501921 Timestamp [UCT]: 2025-11-07 07:52:01 Age [y:d:h:m:s]: 00:046:12:06:49
Block: 1406796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33286 RingCT/type: yes/0
Extra: 014e134d171561f442c79f7b87407301e523540e1a7ce563c809d9997a00b08093021100000003df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f27e02436cc1230cb61477dc940d030e590c85c7dfbed7cd2a41d8dc3c2134cb 0.600000000000 1895185 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": 1406806, "vin": [ { "gen": { "height": 1406796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f27e02436cc1230cb61477dc940d030e590c85c7dfbed7cd2a41d8dc3c2134cb" } } ], "extra": [ 1, 78, 19, 77, 23, 21, 97, 244, 66, 199, 159, 123, 135, 64, 115, 1, 229, 35, 84, 14, 26, 124, 229, 99, 200, 9, 217, 153, 122, 0, 176, 128, 147, 2, 17, 0, 0, 0, 3, 223, 90, 36, 122, 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