Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fce0e876c96ffed2d76ffc26f002d3ae7f2529f219090ae857c504ff6b37bc1f

Tx prefix hash: b5952992e47ff5573511616c82ad31882f5d447a98054d9456c09f0ef45d4070
Tx public key: 000f5ef306155d84cbcc1da2521bee281b51e0b11f35d54e254d382a798c27c1
Timestamp: 1760840917 Timestamp [UCT]: 2025-10-19 02:28:37 Age [y:d:h:m:s]: 00:076:13:40:26
Block: 1393039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54819 RingCT/type: yes/0
Extra: 01000f5ef306155d84cbcc1da2521bee281b51e0b11f35d54e254d382a798c27c1021100000003df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77567c0d42960cdcc40a2d5da3d259fa3c41cf0240e509f89b597f40cf157391 0.600000000000 1881296 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": 1393049, "vin": [ { "gen": { "height": 1393039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77567c0d42960cdcc40a2d5da3d259fa3c41cf0240e509f89b597f40cf157391" } } ], "extra": [ 1, 0, 15, 94, 243, 6, 21, 93, 132, 203, 204, 29, 162, 82, 27, 238, 40, 27, 81, 224, 177, 31, 53, 213, 78, 37, 77, 56, 42, 121, 140, 39, 193, 2, 17, 0, 0, 0, 3, 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