Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 608a717fea64ebd28ffe1c9d822661769dac4ab1c03f812c376b31e9528f4bed

Tx prefix hash: c750de6ea6f133baab4c038ca39237c4f0bf6caded0e26616eda9854d7094b0f
Tx public key: edc851d33daaecc977f191a527e947f6c837160ce97a2db5030dceb7c385e027
Timestamp: 1687735339 Timestamp [UCT]: 2023-06-25 23:22:19 Age [y:d:h:m:s]: 01:297:07:23:19
Block: 790327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473637 RingCT/type: yes/0
Extra: 01edc851d33daaecc977f191a527e947f6c837160ce97a2db5030dceb7c385e027021100000001faf35c9c000000000000000000

1 output(s) for total of 1.476789897000 dcy

stealth address amount amount idx
00: 03e2def02f7fbd69d0d28c9a5067d691ecb79635590436635765bcc1ff313a75 1.476789897000 1240642 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": 790337, "vin": [ { "gen": { "height": 790327 } } ], "vout": [ { "amount": 1476789897, "target": { "key": "03e2def02f7fbd69d0d28c9a5067d691ecb79635590436635765bcc1ff313a75" } } ], "extra": [ 1, 237, 200, 81, 211, 61, 170, 236, 201, 119, 241, 145, 165, 39, 233, 71, 246, 200, 55, 22, 12, 233, 122, 45, 181, 3, 13, 206, 183, 195, 133, 224, 39, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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