Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: add0026d2e4e0fc04a0255bf4db10617065e39e1af761a3c278a642b392249cb

Tx prefix hash: 6754e81501eeb7c00f77d04c413c2590cddb7c8bc599b28c0bb8fc58826dafdc
Tx public key: c59b88819b8e1f2aceedfd7c4a8564b423407a853956351ef843b7c35e6e82fd
Timestamp: 1754698605 Timestamp [UCT]: 2025-08-09 00:16:45 Age [y:d:h:m:s]: 00:008:18:39:10
Block: 1343148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5534 RingCT/type: yes/0
Extra: 01c59b88819b8e1f2aceedfd7c4a8564b423407a853956351ef843b7c35e6e82fd021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6ad1d7acd233217e31446448395871aa416ca5296e567eb062b55e4df633acc 0.600000000000 1830983 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": 1343158, "vin": [ { "gen": { "height": 1343148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6ad1d7acd233217e31446448395871aa416ca5296e567eb062b55e4df633acc" } } ], "extra": [ 1, 197, 155, 136, 129, 155, 142, 31, 42, 206, 237, 253, 124, 74, 133, 100, 180, 35, 64, 122, 133, 57, 86, 53, 30, 248, 67, 183, 195, 94, 110, 130, 253, 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