Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 069ff2e41fa5a230f6ad910b292e4bb5b9c224794bc9449a53765117005c4df8

Tx prefix hash: 98b07945d067dbdc444ddbb081789367e71dbf13587ade9fbc4ceee496fda8ee
Tx public key: 2ddddb79750d71b243f0abfbb63d6f9f5a2c8439dfdcc548bf50c9bb67fff2a3
Timestamp: 1711130464 Timestamp [UCT]: 2024-03-22 18:01:04 Age [y:d:h:m:s]: 01:088:00:35:39
Block: 984042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323785 RingCT/type: yes/0
Extra: 012ddddb79750d71b243f0abfbb63d6f9f5a2c8439dfdcc548bf50c9bb67fff2a302110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1ac82eefe18daccd23dbfe657b6844d360d84b46fd48a7564ef1ace5a1e5fa6 0.600000000000 1444197 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": 984052, "vin": [ { "gen": { "height": 984042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1ac82eefe18daccd23dbfe657b6844d360d84b46fd48a7564ef1ace5a1e5fa6" } } ], "extra": [ 1, 45, 221, 219, 121, 117, 13, 113, 178, 67, 240, 171, 251, 182, 61, 111, 159, 90, 44, 132, 57, 223, 220, 197, 72, 191, 80, 201, 187, 103, 255, 242, 163, 2, 17, 0, 0, 0, 5, 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