Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c00c56d551593c6f38cd9a045ab1b48c2a62a9abf1e617bb45eb54c470aa7bc

Tx prefix hash: 76a34405de62a54d8423e2be620776b140a548b3cdec51b9184f66dc9216095b
Tx public key: 471d0a37aead20389f9c65cfcd6b8991fa2a4676ae919713aa4bb7879fbe8acb
Timestamp: 1765981067 Timestamp [UCT]: 2025-12-17 14:17:47 Age [y:d:h:m:s]: 00:004:22:42:41
Block: 1435623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3547 RingCT/type: yes/0
Extra: 01471d0a37aead20389f9c65cfcd6b8991fa2a4676ae919713aa4bb7879fbe8acb021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b92aa247cd3b253b5fc8cd6b19a0620295aa3550a580279381bd5fa3a80ed66a 0.600000000000 1924420 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": 1435633, "vin": [ { "gen": { "height": 1435623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b92aa247cd3b253b5fc8cd6b19a0620295aa3550a580279381bd5fa3a80ed66a" } } ], "extra": [ 1, 71, 29, 10, 55, 174, 173, 32, 56, 159, 156, 101, 207, 205, 107, 137, 145, 250, 42, 70, 118, 174, 145, 151, 19, 170, 75, 183, 135, 159, 190, 138, 203, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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