Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 979954d52dba5ac817232bb79552e2e57e133de0343922d66b272eae581cacac

Tx prefix hash: 6a0d92dc3e6bbffdf566eae5a1d8bf6785309b5858a3c4555ca028080243aa2f
Tx public key: 956709a04addb20cd004b2ac5d3dc0de00f283f3bb20124c78791d1260cc1d8c
Timestamp: 1751390192 Timestamp [UCT]: 2025-07-01 17:16:32 Age [y:d:h:m:s]: 00:140:16:21:45
Block: 1316663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98769 RingCT/type: yes/0
Extra: 01956709a04addb20cd004b2ac5d3dc0de00f283f3bb20124c78791d1260cc1d8c021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55b7bddece3082f3e80e016b429f327e0341bfdf0a248d6b76f1805b16e5e191 0.600000000000 1804324 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": 1316673, "vin": [ { "gen": { "height": 1316663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55b7bddece3082f3e80e016b429f327e0341bfdf0a248d6b76f1805b16e5e191" } } ], "extra": [ 1, 149, 103, 9, 160, 74, 221, 178, 12, 208, 4, 178, 172, 93, 61, 192, 222, 0, 242, 131, 243, 187, 32, 18, 76, 120, 121, 29, 18, 96, 204, 29, 140, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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