Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9c7c20359f1c599216b1677c119a240a7cf923bcac4655c4a87f94c3dcbb52b

Tx prefix hash: 18f20b8b7fb0ac5f8e04548895f6be05091eb3700f85e19d94406327f33f1ba3
Tx public key: 66c919249ab9d898a16ce63926f09e1ebcf825c42e6c091de957413447fb326f
Timestamp: 1712943473 Timestamp [UCT]: 2024-04-12 17:37:53 Age [y:d:h:m:s]: 01:042:16:00:46
Block: 999031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291502 RingCT/type: yes/0
Extra: 0166c919249ab9d898a16ce63926f09e1ebcf825c42e6c091de957413447fb326f02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a24000f9524964dfb6231daf5943ef659b33cd4e6e66feb9ed22aae4e32e3e4b 0.600000000000 1459507 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": 999041, "vin": [ { "gen": { "height": 999031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a24000f9524964dfb6231daf5943ef659b33cd4e6e66feb9ed22aae4e32e3e4b" } } ], "extra": [ 1, 102, 201, 25, 36, 154, 185, 216, 152, 161, 108, 230, 57, 38, 240, 158, 30, 188, 248, 37, 196, 46, 108, 9, 29, 233, 87, 65, 52, 71, 251, 50, 111, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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