Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9cdb6fdeda72f4298cbf6a6360e28d75b31877caed82d7678dda3397ed1c1c5

Tx prefix hash: 0e61adad74a1ed58acc7d6cb1676004d9137639accb6f685d7ab1326b6659d96
Tx public key: c476aa6e578860cb12a47836aa68dbfc2966dc0e8d1d784de1da0b9073e4000b
Timestamp: 1708207610 Timestamp [UCT]: 2024-02-17 22:06:50 Age [y:d:h:m:s]: 01:036:16:21:26
Block: 959789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287241 RingCT/type: yes/0
Extra: 01c476aa6e578860cb12a47836aa68dbfc2966dc0e8d1d784de1da0b9073e4000b02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85a96dd99701721ad86d2a7e5660e47a01a4b523686e26c5ccb2a49bbecefdbf 0.600000000000 1419342 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": 959799, "vin": [ { "gen": { "height": 959789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85a96dd99701721ad86d2a7e5660e47a01a4b523686e26c5ccb2a49bbecefdbf" } } ], "extra": [ 1, 196, 118, 170, 110, 87, 136, 96, 203, 18, 164, 120, 54, 170, 104, 219, 252, 41, 102, 220, 14, 141, 29, 120, 77, 225, 218, 11, 144, 115, 228, 0, 11, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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