Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bffc4aeb332043680487d5c06d59add014206b34c84b27bf5c0dbf443ed4ef3

Tx prefix hash: 932af781134bf6c97600633fe7852fab2b491f9879711b5dc932ee1e066d255c
Tx public key: d2452e64c1270cc8eba2ee94baa171d3eabae0f8f56c890d0501a1f6d9a765d2
Timestamp: 1744422627 Timestamp [UCT]: 2025-04-12 01:50:27 Age [y:d:h:m:s]: 00:295:08:09:19
Block: 1259533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208719 RingCT/type: yes/0
Extra: 01d2452e64c1270cc8eba2ee94baa171d3eabae0f8f56c890d0501a1f6d9a765d2021100000005dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 626aa17ecfe476adebab9dbcae7a4c7f2c7f80ec877706c09dd7577a8b0cef73 0.600000000000 1746678 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": 1259543, "vin": [ { "gen": { "height": 1259533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "626aa17ecfe476adebab9dbcae7a4c7f2c7f80ec877706c09dd7577a8b0cef73" } } ], "extra": [ 1, 210, 69, 46, 100, 193, 39, 12, 200, 235, 162, 238, 148, 186, 161, 113, 211, 234, 186, 224, 248, 245, 108, 137, 13, 5, 1, 161, 246, 217, 167, 101, 210, 2, 17, 0, 0, 0, 5, 219, 181, 113, 193, 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