Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d0aee3a41afc07e105a1635b1caf0ddf3e06b6436869784a37473a31cf36598

Tx prefix hash: eea2db6b8b236186354d92bdf9a15d18978839caee58605975a4b9db4f993744
Tx public key: a8771c548a13b73941d37f13eaceb6116b9d06a019940dfa4f2e7251b12a9ccb
Timestamp: 1759981649 Timestamp [UCT]: 2025-10-09 03:47:29 Age [y:d:h:m:s]: 00:031:15:53:24
Block: 1385907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22676 RingCT/type: yes/0
Extra: 01a8771c548a13b73941d37f13eaceb6116b9d06a019940dfa4f2e7251b12a9ccb021100000002a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c09f915692827f6f9defd9546f67a52ea1e7274081d354fb1633b3a9d3b58d2 0.600000000000 1874070 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": 1385917, "vin": [ { "gen": { "height": 1385907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c09f915692827f6f9defd9546f67a52ea1e7274081d354fb1633b3a9d3b58d2" } } ], "extra": [ 1, 168, 119, 28, 84, 138, 19, 183, 57, 65, 211, 127, 19, 234, 206, 182, 17, 107, 157, 6, 160, 25, 148, 13, 250, 79, 46, 114, 81, 177, 42, 156, 203, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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