Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e22d3efede7b43b4af965934a264bdc0a6fd98c2c47c4c026f0daf15651906b

Tx prefix hash: 070b996df22124f6d1d337332e5a005258ba5186cb4d6d3998426e84765f5517
Tx public key: 7fe2d50e8c02c6ba5ff5de4cce50a9b12d81c4c1a8300f552ca5d7a4ffe9f5a5
Timestamp: 1764045490 Timestamp [UCT]: 2025-11-25 04:38:10 Age [y:d:h:m:s]: 00:003:01:36:40
Block: 1419589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2193 RingCT/type: yes/0
Extra: 017fe2d50e8c02c6ba5ff5de4cce50a9b12d81c4c1a8300f552ca5d7a4ffe9f5a502110000000217b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c336a5ab65ae4d89c8634360e71d81d7f8ac5c31f3e7bf88602d5414b19c562 0.600000000000 1908126 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": 1419599, "vin": [ { "gen": { "height": 1419589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c336a5ab65ae4d89c8634360e71d81d7f8ac5c31f3e7bf88602d5414b19c562" } } ], "extra": [ 1, 127, 226, 213, 14, 140, 2, 198, 186, 95, 245, 222, 76, 206, 80, 169, 177, 45, 129, 196, 193, 168, 48, 15, 85, 44, 165, 215, 164, 255, 233, 245, 165, 2, 17, 0, 0, 0, 2, 23, 177, 145, 50, 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