Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b12899eade1c84dfe11aa14334953271de365071c985052619c8eaf1719b49e

Tx prefix hash: 5ffb41b26eb01829fcb3a6b8ab57c85a385bb2c165d763d36c4b6ab8e497c5ff
Tx public key: 7c68c3b6672bd8a2018af0bc788b2ad086aff740a1b7a4a4c5f93484f10a827e
Timestamp: 1762554418 Timestamp [UCT]: 2025-11-07 22:26:58 Age [y:d:h:m:s]: 00:061:17:10:13
Block: 1407235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44183 RingCT/type: yes/0
Extra: 017c68c3b6672bd8a2018af0bc788b2ad086aff740a1b7a4a4c5f93484f10a827e02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ffd018b64ba60ffd23d292b0bf738a7c76b658b48e5dea856955beb8423d9b0 0.600000000000 1895646 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": 1407245, "vin": [ { "gen": { "height": 1407235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ffd018b64ba60ffd23d292b0bf738a7c76b658b48e5dea856955beb8423d9b0" } } ], "extra": [ 1, 124, 104, 195, 182, 103, 43, 216, 162, 1, 138, 240, 188, 120, 139, 42, 208, 134, 175, 247, 64, 161, 183, 164, 164, 197, 249, 52, 132, 241, 10, 130, 126, 2, 17, 0, 0, 0, 3, 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