Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f63010095996a003b241f81e2fc7d438caca932e8f6477354d85eced24db9a2

Tx prefix hash: 8d285b2e05bc37819bec6bfd3a1d2dead32921a9de2ec42b5a90914fa3a40ff1
Tx public key: 8898ed24f0b86b1d2ceb5331f7dd217899ad1d5c9d5cc5ae69fe9542345e2949
Timestamp: 1759593063 Timestamp [UCT]: 2025-10-04 15:51:03 Age [y:d:h:m:s]: 00:003:18:04:40
Block: 1382687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2673 RingCT/type: yes/0
Extra: 018898ed24f0b86b1d2ceb5331f7dd217899ad1d5c9d5cc5ae69fe9542345e2949021100000001a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b15c39fcadbb4ef21d705d033312a687f79e1322a72d2d6f131593a7e8346ac 0.600000000000 1870822 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": 1382697, "vin": [ { "gen": { "height": 1382687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b15c39fcadbb4ef21d705d033312a687f79e1322a72d2d6f131593a7e8346ac" } } ], "extra": [ 1, 136, 152, 237, 36, 240, 184, 107, 29, 44, 235, 83, 49, 247, 221, 33, 120, 153, 173, 29, 92, 157, 92, 197, 174, 105, 254, 149, 66, 52, 94, 41, 73, 2, 17, 0, 0, 0, 1, 165, 220, 205, 121, 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