Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8bb70c930d26e9949c54fa1e452c8ecdb36fc7f5d90fe8ab8a51a9596c731ba

Tx prefix hash: e153c2a7e976fe1f22a04ca876083d9ee65c024172fb3426ec14a4725acc7735
Tx public key: b06a60cfb6364d266b2b9bbc9c8609a0e170e762ada2dd0c04dad974dbeb85b3
Timestamp: 1750595072 Timestamp [UCT]: 2025-06-22 12:24:32 Age [y:d:h:m:s]: 00:146:05:25:59
Block: 1310440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102373 RingCT/type: yes/0
Extra: 01b06a60cfb6364d266b2b9bbc9c8609a0e170e762ada2dd0c04dad974dbeb85b3021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87850effa690f7c9c1b291de52e62f01d9abc0faff0cec90b2176f16b900fea5 0.600000000000 1798061 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": 1310450, "vin": [ { "gen": { "height": 1310440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87850effa690f7c9c1b291de52e62f01d9abc0faff0cec90b2176f16b900fea5" } } ], "extra": [ 1, 176, 106, 96, 207, 182, 54, 77, 38, 107, 43, 155, 188, 156, 134, 9, 160, 225, 112, 231, 98, 173, 162, 221, 12, 4, 218, 217, 116, 219, 235, 133, 179, 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