Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4376e26b7fb48c768bd32e7b443ddb09c2401d0c5ceb0f5d99a3cf646c3589ee

Tx prefix hash: 1ed30ed1caea1712e69ee83dc3d9636e5f3a05a14af92dc87a0fe8a39a8bcf42
Tx public key: eda62574e6d9d713dc37ed93e1f4ff1373e6992f42d913186997ed1d849001bd
Timestamp: 1753269387 Timestamp [UCT]: 2025-07-23 11:16:27 Age [y:d:h:m:s]: 00:120:10:30:14
Block: 1331607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84904 RingCT/type: yes/0
Extra: 01eda62574e6d9d713dc37ed93e1f4ff1373e6992f42d913186997ed1d849001bd021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 148423e68f183f5acc7330d712818b833bc9823320427f0add0c75ce0ccb2f2e 0.600000000000 1819402 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": 1331617, "vin": [ { "gen": { "height": 1331607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "148423e68f183f5acc7330d712818b833bc9823320427f0add0c75ce0ccb2f2e" } } ], "extra": [ 1, 237, 166, 37, 116, 230, 217, 215, 19, 220, 55, 237, 147, 225, 244, 255, 19, 115, 230, 153, 47, 66, 217, 19, 24, 105, 151, 237, 29, 132, 144, 1, 189, 2, 17, 0, 0, 0, 2, 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