Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a85d8e376508bbc90b72bdf39eb4879f0e147cd14ab12202c38442a43608f43

Tx prefix hash: b2363f99dadedeb2c3ba1243278ded63db9e7e99b5a2500106e721b31cf3f2ed
Tx public key: e9b8f802bbbe0843833627e2a7c5ce21a6d4fa0ed2d9868ac288b0eeb27a032f
Timestamp: 1702823514 Timestamp [UCT]: 2023-12-17 14:31:54 Age [y:d:h:m:s]: 01:033:20:57:22
Block: 915151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285529 RingCT/type: yes/0
Extra: 01e9b8f802bbbe0843833627e2a7c5ce21a6d4fa0ed2d9868ac288b0eeb27a032f021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d65394da8c7ee08d0517ed90e57341fdca7c5055d07c0ba8954b74bca4d80311 0.600000000000 1372537 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": 915161, "vin": [ { "gen": { "height": 915151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d65394da8c7ee08d0517ed90e57341fdca7c5055d07c0ba8954b74bca4d80311" } } ], "extra": [ 1, 233, 184, 248, 2, 187, 190, 8, 67, 131, 54, 39, 226, 167, 197, 206, 33, 166, 212, 250, 14, 210, 217, 134, 138, 194, 136, 176, 238, 178, 122, 3, 47, 2, 17, 0, 0, 0, 2, 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