Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 434106ed70969a97677d3da4383d63e92a7dccd40cc813b4c498a4313f209dd9

Tx prefix hash: 18507ca55ddc5a824470db2e701ee439c6d7e05a101bdb7bb062383bca8e8a12
Tx public key: ce84bf247db077384e2e6e194b9d6c2a5d17b7a30615f6eb504bdd77ed8e2ef6
Timestamp: 1685363059 Timestamp [UCT]: 2023-05-29 12:24:19 Age [y:d:h:m:s]: 02:163:15:04:58
Block: 770656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 636722 RingCT/type: yes/0
Extra: 01ce84bf247db077384e2e6e194b9d6c2a5d17b7a30615f6eb504bdd77ed8e2ef6021100000001b3164c24000000000000000000

1 output(s) for total of 1.715919582000 dcy

stealth address amount amount idx
00: 0a0c5ae4a132de61104a7878a63239f862dadef3475effab26796b88efb2666f 1.715919582000 1219983 of 0

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": 770666, "vin": [ { "gen": { "height": 770656 } } ], "vout": [ { "amount": 1715919582, "target": { "key": "0a0c5ae4a132de61104a7878a63239f862dadef3475effab26796b88efb2666f" } } ], "extra": [ 1, 206, 132, 191, 36, 125, 176, 119, 56, 78, 46, 110, 25, 75, 157, 108, 42, 93, 23, 183, 163, 6, 21, 246, 235, 80, 75, 221, 119, 237, 142, 46, 246, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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