Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acd7ddfd760d10aaf4481f1fff9e416b60654456fc23b6db44504edfd093ace0

Tx prefix hash: 6878f8080a25eb362611763e0f1068e747afb80b44e2cb76bc199fa986144a13
Tx public key: b8e2b1a8d213b16c0ba7618b8c5e6039a7638b5b8070c17c5f80f1f86161d71b
Timestamp: 1737519109 Timestamp [UCT]: 2025-01-22 04:11:49 Age [y:d:h:m:s]: 00:148:21:34:10
Block: 1202601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106140 RingCT/type: yes/0
Extra: 01b8e2b1a8d213b16c0ba7618b8c5e6039a7638b5b8070c17c5f80f1f86161d71b0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e1402b66b562513862344186ad7284a14340673351563ef91dfaf2fb3435b4a 0.600000000000 1689266 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": 1202611, "vin": [ { "gen": { "height": 1202601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e1402b66b562513862344186ad7284a14340673351563ef91dfaf2fb3435b4a" } } ], "extra": [ 1, 184, 226, 177, 168, 210, 19, 177, 108, 11, 167, 97, 139, 140, 94, 96, 57, 167, 99, 139, 91, 128, 112, 193, 124, 95, 128, 241, 248, 97, 97, 215, 27, 2, 17, 0, 0, 0, 3, 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