Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6426db289e55a0b4e9cdcfb7d5a69c3eeb15ec211d25b52737d1160583fe7e5

Tx prefix hash: 1eaca801a19502901bcded3cb8861643caa53796b0380f7e16d50f1f930ee487
Tx public key: 4c06de7051eb5e6b6e395df8ae6fca470df823855f4c9bc35e53152785349c7b
Timestamp: 1717214671 Timestamp [UCT]: 2024-06-01 04:04:31 Age [y:d:h:m:s]: 00:298:09:00:41
Block: 1034468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213227 RingCT/type: yes/0
Extra: 014c06de7051eb5e6b6e395df8ae6fca470df823855f4c9bc35e53152785349c7b02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 009e5985e59a3657cdeb9771eab51c36855cb8a5596f79c5017bead9561e536a 0.600000000000 1502981 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": 1034478, "vin": [ { "gen": { "height": 1034468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "009e5985e59a3657cdeb9771eab51c36855cb8a5596f79c5017bead9561e536a" } } ], "extra": [ 1, 76, 6, 222, 112, 81, 235, 94, 107, 110, 57, 93, 248, 174, 111, 202, 71, 13, 248, 35, 133, 95, 76, 155, 195, 94, 83, 21, 39, 133, 52, 156, 123, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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