Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2233e49c1d1777437c78b9ad2f6d4f24018bf2b11544f553f08de18cf1c8daa0

Tx prefix hash: 6bbeffe80c03f775a2c13ec2fae05815293b8f6a107455f48ee50a3ad782536b
Tx public key: 238d0b8a56805c504ce9df90e94eacb781b8da396d245303347101ff3f0f3f67
Timestamp: 1750308706 Timestamp [UCT]: 2025-06-19 04:51:46 Age [y:d:h:m:s]: 00:148:20:24:19
Block: 1308121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104204 RingCT/type: yes/0
Extra: 01238d0b8a56805c504ce9df90e94eacb781b8da396d245303347101ff3f0f3f67021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ece69739cbf075b40f34b31a9dc568235b074e9812d5862e39f7769c342be91e 0.600000000000 1795734 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": 1308131, "vin": [ { "gen": { "height": 1308121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ece69739cbf075b40f34b31a9dc568235b074e9812d5862e39f7769c342be91e" } } ], "extra": [ 1, 35, 141, 11, 138, 86, 128, 92, 80, 76, 233, 223, 144, 233, 78, 172, 183, 129, 184, 218, 57, 109, 36, 83, 3, 52, 113, 1, 255, 63, 15, 63, 103, 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