Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1c6f7cf51b5b674d185514638e2f04e28ee2be3bdd7833fa8a13176c2ab4d59

Tx prefix hash: 51e85fefa0c818d687162c33d29fc612a8f3fdf874a40d6b1deea8b8fdf7cc41
Tx public key: 218eae5cfa6f3eedd1b330504e2f99ddae7c08ff6b342f9a33ffa154cab2c37c
Timestamp: 1762710088 Timestamp [UCT]: 2025-11-09 17:41:28 Age [y:d:h:m:s]: 00:056:05:43:26
Block: 1408524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40281 RingCT/type: yes/0
Extra: 01218eae5cfa6f3eedd1b330504e2f99ddae7c08ff6b342f9a33ffa154cab2c37c0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdc3715e15b33d794528d2c1c052aad2ed88e94bbd5cf1bd8a68bcd260f25178 0.600000000000 1896953 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": 1408534, "vin": [ { "gen": { "height": 1408524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdc3715e15b33d794528d2c1c052aad2ed88e94bbd5cf1bd8a68bcd260f25178" } } ], "extra": [ 1, 33, 142, 174, 92, 250, 111, 62, 237, 209, 179, 48, 80, 78, 47, 153, 221, 174, 124, 8, 255, 107, 52, 47, 154, 51, 255, 161, 84, 202, 178, 195, 124, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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