Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b684d098d0cdbe44be3968adea6f6d784c527cddcc1fe37e9acc19f6571c313b

Tx prefix hash: 90def71d0260d5eb5cd61679a7ad61c7e8648fbd191bf8dc27a204b9c88e65a9
Tx public key: 3fa8faee8e0d91889a0c2e758c66c7d77d55bfc555e106ee865cd93466cc1c2f
Timestamp: 1744940547 Timestamp [UCT]: 2025-04-18 01:42:27 Age [y:d:h:m:s]: 00:206:23:32:26
Block: 1263811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145646 RingCT/type: yes/0
Extra: 013fa8faee8e0d91889a0c2e758c66c7d77d55bfc555e106ee865cd93466cc1c2f02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fd79bd35731284d65203c9d7fc4a125faef5b0991d5c5f34a7440f5d42dded4 0.600000000000 1751004 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": 1263821, "vin": [ { "gen": { "height": 1263811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fd79bd35731284d65203c9d7fc4a125faef5b0991d5c5f34a7440f5d42dded4" } } ], "extra": [ 1, 63, 168, 250, 238, 142, 13, 145, 136, 154, 12, 46, 117, 140, 102, 199, 215, 125, 85, 191, 197, 85, 225, 6, 238, 134, 92, 217, 52, 102, 204, 28, 47, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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