Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd68136276050e442ac07e65567aef8622f899bab8b0264470b1c627ade8f0dd

Tx prefix hash: b1dc6ac51c50d631648241bfdf4e08b22c7f148dff83a1e456f0b3c6159fa8c7
Tx public key: c80e391c2281f60a0fa0b18c2ad999b40ea5d1ac71839247b4f0a7316783b583
Timestamp: 1751286554 Timestamp [UCT]: 2025-06-30 12:29:14 Age [y:d:h:m:s]: 00:140:20:48:25
Block: 1315844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98870 RingCT/type: yes/0
Extra: 01c80e391c2281f60a0fa0b18c2ad999b40ea5d1ac71839247b4f0a7316783b583021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a177b7959bd58a36746eeb2a6f9d602608df5b58434b397c90273326d741f7a 0.600000000000 1803501 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": 1315854, "vin": [ { "gen": { "height": 1315844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a177b7959bd58a36746eeb2a6f9d602608df5b58434b397c90273326d741f7a" } } ], "extra": [ 1, 200, 14, 57, 28, 34, 129, 246, 10, 15, 160, 177, 140, 42, 217, 153, 180, 14, 165, 209, 172, 113, 131, 146, 71, 180, 240, 167, 49, 103, 131, 181, 131, 2, 17, 0, 0, 0, 2, 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