Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85add82b46f8cf8bb0617d76a908054479556f84d0bf8f198e0fa7f888beb25e

Tx prefix hash: cc36d890108b1b6e05b25b29865e4f65a09616316dc98ad5842be68d5a03d6c8
Tx public key: 4807653b054ea12bcbe3d0ce78bc988df91e786e32ba2c8724531a20ae45da19
Timestamp: 1759921394 Timestamp [UCT]: 2025-10-08 11:03:14 Age [y:d:h:m:s]: 00:092:19:53:27
Block: 1385398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66479 RingCT/type: yes/0
Extra: 014807653b054ea12bcbe3d0ce78bc988df91e786e32ba2c8724531a20ae45da19021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44cc39ec1b860c118e3e3e72c5f1d78dea5be8829f122a840f470d13a28692d8 0.600000000000 1873561 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": 1385408, "vin": [ { "gen": { "height": 1385398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44cc39ec1b860c118e3e3e72c5f1d78dea5be8829f122a840f470d13a28692d8" } } ], "extra": [ 1, 72, 7, 101, 59, 5, 78, 161, 43, 203, 227, 208, 206, 120, 188, 152, 141, 249, 30, 120, 110, 50, 186, 44, 135, 36, 83, 26, 32, 174, 69, 218, 25, 2, 17, 0, 0, 0, 4, 216, 231, 210, 65, 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