Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b952d8be57865a3aa3129688bf9d2a9d2e44a142bd5fb5613af7113623bfdd96

Tx prefix hash: 8a747f7751e466ff3ee14f03ad9d704467a2248d807adda7961c4b9dd9c6f54e
Tx public key: ca9cf3a936a5946e473e3ba999b41dc8c9f7424a7e9de189d17a48df853d7c29
Timestamp: 1720501213 Timestamp [UCT]: 2024-07-09 05:00:13 Age [y:d:h:m:s]: 00:310:17:20:17
Block: 1061718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222018 RingCT/type: yes/0
Extra: 01ca9cf3a936a5946e473e3ba999b41dc8c9f7424a7e9de189d17a48df853d7c2902110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 490082338fbf0b0fc4dbadf151551144b1c46b1940354346fa9866a5537c4eb4 0.600000000000 1532213 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": 1061728, "vin": [ { "gen": { "height": 1061718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "490082338fbf0b0fc4dbadf151551144b1c46b1940354346fa9866a5537c4eb4" } } ], "extra": [ 1, 202, 156, 243, 169, 54, 165, 148, 110, 71, 62, 59, 169, 153, 180, 29, 200, 201, 247, 66, 74, 126, 157, 225, 137, 209, 122, 72, 223, 133, 61, 124, 41, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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