Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1af53f7f6159a9744c412ffda12e207c651f0f4fbb64a8cd1ec05d1646855b37

Tx prefix hash: 9a5bf21101beca0658de0516b01fae58498377f60f74998e81c71c1cbff847ca
Tx public key: 047e00ddb513c95233819e56cb3ffeaa409a68734d6b026c79c3c6cf0c62c8cf
Timestamp: 1738274467 Timestamp [UCT]: 2025-01-30 22:01:07 Age [y:d:h:m:s]: 00:042:01:20:06
Block: 1208637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30093 RingCT/type: yes/0
Extra: 01047e00ddb513c95233819e56cb3ffeaa409a68734d6b026c79c3c6cf0c62c8cf021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffbbd03caf260d2fa1b7d8c9b1bff509b8fdb8128f53418641420e5ce06e51d8 0.600000000000 1695370 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": 1208647, "vin": [ { "gen": { "height": 1208637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffbbd03caf260d2fa1b7d8c9b1bff509b8fdb8128f53418641420e5ce06e51d8" } } ], "extra": [ 1, 4, 126, 0, 221, 181, 19, 201, 82, 51, 129, 158, 86, 203, 63, 254, 170, 64, 154, 104, 115, 77, 107, 2, 108, 121, 195, 198, 207, 12, 98, 200, 207, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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