Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f57d24acb33d7a1319dacdf24aabba22dd318b5cf45651334f0f532768c27ad7

Tx prefix hash: 60f4e95f6c2dd72e304c12f96b890ac2e8f0d6402f69bb22aa01bf210fd90d8c
Tx public key: 578a0c9cb9a1b781ae4a6996bae2ae01709caa3cf11ab5aa1a3ac5a46500b34d
Timestamp: 1751365306 Timestamp [UCT]: 2025-07-01 10:21:46 Age [y:d:h:m:s]: 00:143:14:06:21
Block: 1316478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100829 RingCT/type: yes/0
Extra: 01578a0c9cb9a1b781ae4a6996bae2ae01709caa3cf11ab5aa1a3ac5a46500b34d021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 497d65f4b8561c23a8c76a6777c3c80b66e130d9edaae87eb09f9d8d664daafe 0.600000000000 1804139 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": 1316488, "vin": [ { "gen": { "height": 1316478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "497d65f4b8561c23a8c76a6777c3c80b66e130d9edaae87eb09f9d8d664daafe" } } ], "extra": [ 1, 87, 138, 12, 156, 185, 161, 183, 129, 174, 74, 105, 150, 186, 226, 174, 1, 112, 156, 170, 60, 241, 26, 181, 170, 26, 58, 197, 164, 101, 0, 179, 77, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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