Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 944d690946f2261b545725bbc619f25e02fb69ef48b1aa418c2742f8be65fbbf

Tx prefix hash: 2ab58ee92f635db29c0b4554b86b2d686b6fe76dc620daa72b69a9cb45848bf8
Tx public key: e87a5e7cbc9fc40d41b282b6683eebfbaf3d9c18ce2cc7f25ea40352b105e07e
Timestamp: 1700486412 Timestamp [UCT]: 2023-11-20 13:20:12 Age [y:d:h:m:s]: 01:061:03:50:13
Block: 895771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305078 RingCT/type: yes/0
Extra: 01e87a5e7cbc9fc40d41b282b6683eebfbaf3d9c18ce2cc7f25ea40352b105e07e02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.660600373000 dcy

stealth address amount amount idx
00: a7af6004e3cf4d1be57d8d5cf03968d5449d8870fbc83b41416fff1ad55c037b 0.660600373000 1352018 of 0

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": 895781, "vin": [ { "gen": { "height": 895771 } } ], "vout": [ { "amount": 660600373, "target": { "key": "a7af6004e3cf4d1be57d8d5cf03968d5449d8870fbc83b41416fff1ad55c037b" } } ], "extra": [ 1, 232, 122, 94, 124, 188, 159, 196, 13, 65, 178, 130, 182, 104, 62, 235, 251, 175, 61, 156, 24, 206, 44, 199, 242, 94, 164, 3, 82, 177, 5, 224, 126, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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