Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16a1544c8e563d08b75b1c0ce90610730420a8ada68be00e69b630abab7723b9

Tx prefix hash: 5d21cda30379a5f5d087f4f6e868d91d7e6aab4fec4ed25829b81c2694dc5633
Tx public key: 178b86bb29d36881c1848829dba82a1aac1f0e7e45ee92bd06d36d8e5170f91c
Timestamp: 1762041732 Timestamp [UCT]: 2025-11-02 00:02:12 Age [y:d:h:m:s]: 00:004:22:13:22
Block: 1402987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3518 RingCT/type: yes/0
Extra: 01178b86bb29d36881c1848829dba82a1aac1f0e7e45ee92bd06d36d8e5170f91c021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30b5cd40e953d764f5b96404d498b4a0f0f2caff4b317fd09c1cde5ec74452d9 0.600000000000 1891314 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": 1402997, "vin": [ { "gen": { "height": 1402987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30b5cd40e953d764f5b96404d498b4a0f0f2caff4b317fd09c1cde5ec74452d9" } } ], "extra": [ 1, 23, 139, 134, 187, 41, 211, 104, 129, 193, 132, 136, 41, 219, 168, 42, 26, 172, 31, 14, 126, 69, 238, 146, 189, 6, 211, 109, 142, 81, 112, 249, 28, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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