Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e0de3a66f97aad6206305c370b132fe7eb8bc6ec9ad96b7a1e53d09311ff08d

Tx prefix hash: 44f20a047ef1d831f2babe6794f0d15739b86fc39a0b1f8001906fe8d1f6183a
Tx public key: 446d6aa3ab514c03df6b7a770bc1c51cb5a75dc0a9427654673550bc698a3adb
Timestamp: 1751226856 Timestamp [UCT]: 2025-06-29 19:54:16 Age [y:d:h:m:s]: 00:187:20:15:02
Block: 1315374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132484 RingCT/type: yes/0
Extra: 01446d6aa3ab514c03df6b7a770bc1c51cb5a75dc0a9427654673550bc698a3adb021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffe86a5b20cde5cc6738548142f1970464f27f8fe0796ea9c39b8607024cd097 0.600000000000 1803029 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": 1315384, "vin": [ { "gen": { "height": 1315374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffe86a5b20cde5cc6738548142f1970464f27f8fe0796ea9c39b8607024cd097" } } ], "extra": [ 1, 68, 109, 106, 163, 171, 81, 76, 3, 223, 107, 122, 119, 11, 193, 197, 28, 181, 167, 93, 192, 169, 66, 118, 84, 103, 53, 80, 188, 105, 138, 58, 219, 2, 17, 0, 0, 0, 4, 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