Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a89e00e6c47ede9d35b74be1fa0538ebfd6ca0e569b852fcef14308d8142e51b

Tx prefix hash: 4a0a4a2a363ef26ecd1e6567c3054c44bbacfe81b0b23aeca2d33164451468e2
Tx public key: 6aedf8abbbadcb6ff152676190dc734a8e009d8d1f5a38df6d93df8140e445ec
Timestamp: 1744540777 Timestamp [UCT]: 2025-04-13 10:39:37 Age [y:d:h:m:s]: 00:029:06:05:59
Block: 1260506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20925 RingCT/type: yes/0
Extra: 016aedf8abbbadcb6ff152676190dc734a8e009d8d1f5a38df6d93df8140e445ec0211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb488967595c5ad06cc02dde4f5187b850a6d2fefdf51e6350e9aa712651e265 0.600000000000 1747665 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": 1260516, "vin": [ { "gen": { "height": 1260506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb488967595c5ad06cc02dde4f5187b850a6d2fefdf51e6350e9aa712651e265" } } ], "extra": [ 1, 106, 237, 248, 171, 187, 173, 203, 111, 241, 82, 103, 97, 144, 220, 115, 74, 142, 0, 157, 141, 31, 90, 56, 223, 109, 147, 223, 129, 64, 228, 69, 236, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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