Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d910c958d3d301fb68ac34944f474ca9daba90fdf93f43f9c41311a69a6f320

Tx prefix hash: ff2901928f5cb9601b6d6ba07ede360e2af4a224fa55e6188819b4435fc901c8
Tx public key: a996d9448dbb27d80e8f5468ec2304bab07f7b16f8dc3267707f2de47d48bf3f
Timestamp: 1752511826 Timestamp [UCT]: 2025-07-14 16:50:26 Age [y:d:h:m:s]: 00:173:23:23:42
Block: 1325440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123150 RingCT/type: yes/0
Extra: 01a996d9448dbb27d80e8f5468ec2304bab07f7b16f8dc3267707f2de47d48bf3f02110000000425a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 026eac88ef389ed7a3ddae0b7b0a9c6dcf7c6aa7c5d3b4c10eeee93411addee5 0.600000000000 1813185 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": 1325450, "vin": [ { "gen": { "height": 1325440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "026eac88ef389ed7a3ddae0b7b0a9c6dcf7c6aa7c5d3b4c10eeee93411addee5" } } ], "extra": [ 1, 169, 150, 217, 68, 141, 187, 39, 216, 14, 143, 84, 104, 236, 35, 4, 186, 176, 127, 123, 22, 248, 220, 50, 103, 112, 127, 45, 228, 125, 72, 191, 63, 2, 17, 0, 0, 0, 4, 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