Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0ac2021b0fcef768f2f9c7f1bfc66ec3a6bd2817a5ae3a89758f32237013690

Tx prefix hash: 5f7a4bab8e38d8fe13490ece1f83d3fe27b97be19c828c80fd44562e791a8ea6
Tx public key: 18a855617d55ff157d1b72cd48586fdafc4aa88619edd38dd1bdd3a7dab2d9bc
Timestamp: 1765357424 Timestamp [UCT]: 2025-12-10 09:03:44 Age [y:d:h:m:s]: 00:026:15:01:49
Block: 1430452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19088 RingCT/type: yes/0
Extra: 0118a855617d55ff157d1b72cd48586fdafc4aa88619edd38dd1bdd3a7dab2d9bc021100000008d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae3228fd975e108ba01939294163e9eb0b8fbe68a46be0d1b8e0d20362b1d1dc 0.600000000000 1919203 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": 1430462, "vin": [ { "gen": { "height": 1430452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae3228fd975e108ba01939294163e9eb0b8fbe68a46be0d1b8e0d20362b1d1dc" } } ], "extra": [ 1, 24, 168, 85, 97, 125, 85, 255, 21, 125, 27, 114, 205, 72, 88, 111, 218, 252, 74, 168, 134, 25, 237, 211, 141, 209, 189, 211, 167, 218, 178, 217, 188, 2, 17, 0, 0, 0, 8, 214, 225, 157, 124, 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