Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84e6e7b72e9fc76a44ee699c4178bb95eb8ba06e2832568a264af3c77bce8527

Tx prefix hash: 5cbc775b97fd656e1d5eecd0ca0d11e5728fd273e79694bcfdc182261b21c534
Tx public key: b0c932824891a2772ba7d69999d21fab245f81604b536dba7daccb4eb1ad1d5f
Timestamp: 1726486894 Timestamp [UCT]: 2024-09-16 11:41:34 Age [y:d:h:m:s]: 01:052:12:10:58
Block: 1111337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295936 RingCT/type: yes/0
Extra: 01b0c932824891a2772ba7d69999d21fab245f81604b536dba7daccb4eb1ad1d5f02110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec3886b518f891d715a9d853d7acc1e7d86ac1582aee6a39ddb772db0652d72b 0.600000000000 1590260 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": 1111347, "vin": [ { "gen": { "height": 1111337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec3886b518f891d715a9d853d7acc1e7d86ac1582aee6a39ddb772db0652d72b" } } ], "extra": [ 1, 176, 201, 50, 130, 72, 145, 162, 119, 43, 167, 214, 153, 153, 210, 31, 171, 36, 95, 129, 96, 75, 83, 109, 186, 125, 172, 203, 78, 177, 173, 29, 95, 2, 17, 0, 0, 0, 13, 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