Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c65e0f8fa3e651f0fbe332feb12577dd34a518d3b22c7fc8a4bec4b71df4110f

Tx prefix hash: 8d8aad3c6a0249a118532dfbac5ae701704b682c32240efc1259e1514a3eb87f
Tx public key: b71ef7dd980c7307e52ad253eaf6cfe7988d9e6ba04c3fa48c61a8b7a0ab68ec
Timestamp: 1740933359 Timestamp [UCT]: 2025-03-02 16:35:59 Age [y:d:h:m:s]: 00:331:19:48:12
Block: 1230636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234828 RingCT/type: yes/0
Extra: 01b71ef7dd980c7307e52ad253eaf6cfe7988d9e6ba04c3fa48c61a8b7a0ab68ec02110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 087f8867163d8b096d1aa4c195e37665beb159ec4588948d18d17a471f3252ed 0.600000000000 1717535 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": 1230646, "vin": [ { "gen": { "height": 1230636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "087f8867163d8b096d1aa4c195e37665beb159ec4588948d18d17a471f3252ed" } } ], "extra": [ 1, 183, 30, 247, 221, 152, 12, 115, 7, 229, 42, 210, 83, 234, 246, 207, 231, 152, 141, 158, 107, 160, 76, 63, 164, 140, 97, 168, 183, 160, 171, 104, 236, 2, 17, 0, 0, 0, 12, 31, 10, 83, 235, 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