Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dc5a8bb6d7edc8e97a427121c015c20cd3140134a7e51fe0f624e263b9613db

Tx prefix hash: 8265d848f232ec3ed594971c3b2bd37fec1f656429db2955f0369a71e44376e7
Tx public key: 654ce1d78cb5b6fb7b988c9da77a7cd94c0946d1ac71be0ec54ab1a31a488db8
Timestamp: 1753417667 Timestamp [UCT]: 2025-07-25 04:27:47 Age [y:d:h:m:s]: 00:124:10:42:41
Block: 1332841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87775 RingCT/type: yes/0
Extra: 01654ce1d78cb5b6fb7b988c9da77a7cd94c0946d1ac71be0ec54ab1a31a488db8021100000001ef221485000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb334c4598ad9ff9e5955b3c376d42e4a61ae49916be05086fc66f4a87118c1a 0.600000000000 1820640 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": 1332851, "vin": [ { "gen": { "height": 1332841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb334c4598ad9ff9e5955b3c376d42e4a61ae49916be05086fc66f4a87118c1a" } } ], "extra": [ 1, 101, 76, 225, 215, 140, 181, 182, 251, 123, 152, 140, 157, 167, 122, 124, 217, 76, 9, 70, 209, 172, 113, 190, 14, 197, 74, 177, 163, 26, 72, 141, 184, 2, 17, 0, 0, 0, 1, 239, 34, 20, 133, 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