Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d96b2200b557b0296db4d192d908571ac142c2e0d00fa0d1d20ec83415a8a86

Tx prefix hash: 6ee5694b4ead9326d59ed6b7acb516fa13fb8e992170c0e13dc4967588d2ac14
Tx public key: 980c1553addc80bfae0c4d19a80419f7d2d81133350a684c3fdbca056c118305
Timestamp: 1726498644 Timestamp [UCT]: 2024-09-16 14:57:24 Age [y:d:h:m:s]: 00:115:22:29:05
Block: 1111431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82904 RingCT/type: yes/0
Extra: 01980c1553addc80bfae0c4d19a80419f7d2d81133350a684c3fdbca056c118305021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a74dfaf614095c6f96820bf5906ddf9fc17a102e9836f2df4586301f5a60c584 0.600000000000 1590388 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": 1111441, "vin": [ { "gen": { "height": 1111431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a74dfaf614095c6f96820bf5906ddf9fc17a102e9836f2df4586301f5a60c584" } } ], "extra": [ 1, 152, 12, 21, 83, 173, 220, 128, 191, 174, 12, 77, 25, 168, 4, 25, 247, 210, 216, 17, 51, 53, 10, 104, 76, 63, 219, 202, 5, 108, 17, 131, 5, 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