Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4dbeb35a42d444dd76b6d6bbe841f7772478dd69b42922648d8670743e24a9c

Tx prefix hash: f91bd0c355692309d74dcb41b486e8c94e61d547441935aaecd7422d006b3904
Tx public key: 849d5915a40800763ac2b9d4aac47c18ee87d63ff4a9bbf3f8cdd14e4fe3a966
Timestamp: 1749623012 Timestamp [UCT]: 2025-06-11 06:23:32 Age [y:d:h:m:s]: 00:151:21:48:41
Block: 1302575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106259 RingCT/type: yes/0
Extra: 01849d5915a40800763ac2b9d4aac47c18ee87d63ff4a9bbf3f8cdd14e4fe3a966021100000008bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be9221bf75a2d2b6c2ac43ac94a4e26a84d80f2f1c14bbfdaea76b095d6bfbc0 0.600000000000 1790146 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": 1302585, "vin": [ { "gen": { "height": 1302575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be9221bf75a2d2b6c2ac43ac94a4e26a84d80f2f1c14bbfdaea76b095d6bfbc0" } } ], "extra": [ 1, 132, 157, 89, 21, 164, 8, 0, 118, 58, 194, 185, 212, 170, 196, 124, 24, 238, 135, 214, 63, 244, 169, 187, 243, 248, 205, 209, 78, 79, 227, 169, 102, 2, 17, 0, 0, 0, 8, 191, 81, 178, 162, 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