Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc204eab4304b19ef284fe7ec51309f9c5ebfccdd87e2c24e5dbe48a032d4fe8

Tx prefix hash: 20115836d870b4658907080dc9b745de3e2ec2138e42887496632f7575eab374
Tx public key: ca2c05e56263c4468dd6f636cd8b6517801820a024b9cd2e213247d0f8a1d528
Timestamp: 1750335891 Timestamp [UCT]: 2025-06-19 12:24:51 Age [y:d:h:m:s]: 00:191:13:11:17
Block: 1308345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134783 RingCT/type: yes/0
Extra: 01ca2c05e56263c4468dd6f636cd8b6517801820a024b9cd2e213247d0f8a1d528021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0f712696e58dcb6b2de3a549907626f07d4ea319f7c606aadf4d2f3bdda8109 0.600000000000 1795958 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": 1308355, "vin": [ { "gen": { "height": 1308345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0f712696e58dcb6b2de3a549907626f07d4ea319f7c606aadf4d2f3bdda8109" } } ], "extra": [ 1, 202, 44, 5, 229, 98, 99, 196, 70, 141, 214, 246, 54, 205, 139, 101, 23, 128, 24, 32, 160, 36, 185, 205, 46, 33, 50, 71, 208, 248, 161, 213, 40, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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