Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d051ea3573afe08f071d2ef6f7c3a3d2352efe205e6a2e6053a4044c300a7bf8

Tx prefix hash: 066392cb7bed037f3a68c14e4b88d8a84c8c15cd03ced4b2d90a088542d98940
Tx public key: 3744ec57f3b5c0cd46b92306313f0131e524862f2700735ab4dc595a5b739753
Timestamp: 1713840692 Timestamp [UCT]: 2024-04-23 02:51:32 Age [y:d:h:m:s]: 00:308:03:22:32
Block: 1006490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220249 RingCT/type: yes/0
Extra: 013744ec57f3b5c0cd46b92306313f0131e524862f2700735ab4dc595a5b7397530211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 631edf3b745b8026088d540aac505d1442c654117780f30f28e39f777ddb81ee 0.600000000000 1467536 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": 1006500, "vin": [ { "gen": { "height": 1006490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "631edf3b745b8026088d540aac505d1442c654117780f30f28e39f777ddb81ee" } } ], "extra": [ 1, 55, 68, 236, 87, 243, 181, 192, 205, 70, 185, 35, 6, 49, 63, 1, 49, 229, 36, 134, 47, 39, 0, 115, 90, 180, 220, 89, 90, 91, 115, 151, 83, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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