Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac38fa0828d4d0d5d09c68354f352676f6bc77859af497ae2fc3d87a86a9de55

Tx prefix hash: 7aedfb7177d2551d6d1c63a8731565c488f383a952cd3a0663405d597f5bd19e
Tx public key: 934c5f50e5d30aa979c6105e7a56c3450f5b15f626953a5197fd45d8a86aff76
Timestamp: 1760863689 Timestamp [UCT]: 2025-10-19 08:48:09 Age [y:d:h:m:s]: 00:078:14:48:42
Block: 1393236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56295 RingCT/type: yes/0
Extra: 01934c5f50e5d30aa979c6105e7a56c3450f5b15f626953a5197fd45d8a86aff76021100000002df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24f530387a0695aa3692ca8a78f6c1db3aff1047ef7d0863d3824fee35054262 0.600000000000 1881495 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": 1393246, "vin": [ { "gen": { "height": 1393236 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24f530387a0695aa3692ca8a78f6c1db3aff1047ef7d0863d3824fee35054262" } } ], "extra": [ 1, 147, 76, 95, 80, 229, 211, 10, 169, 121, 198, 16, 94, 122, 86, 195, 69, 15, 91, 21, 246, 38, 149, 58, 81, 151, 253, 69, 216, 168, 106, 255, 118, 2, 17, 0, 0, 0, 2, 223, 90, 36, 122, 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