Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac3ccce25339930a5e607f51703f41fa23eff7af088c167ae3db2d3d9e065323

Tx prefix hash: d21675c5e9a479673633bcedc0d0f5c665fca35d97ec3a54fbdab8ea84be6ae5
Tx public key: a5a599affbc182ca49580a380db1cdba968790b37870e3f1f3f4e1a6ff94eaf6
Timestamp: 1754617162 Timestamp [UCT]: 2025-08-08 01:39:22 Age [y:d:h:m:s]: 00:053:17:35:57
Block: 1342492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37422 RingCT/type: yes/0
Extra: 01a5a599affbc182ca49580a380db1cdba968790b37870e3f1f3f4e1a6ff94eaf602110000000425a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c15a5d9256246446b70b70f150c8e356f78021305ee5632ff144fd7382d419d5 0.600000000000 1830323 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": 1342502, "vin": [ { "gen": { "height": 1342492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c15a5d9256246446b70b70f150c8e356f78021305ee5632ff144fd7382d419d5" } } ], "extra": [ 1, 165, 165, 153, 175, 251, 193, 130, 202, 73, 88, 10, 56, 13, 177, 205, 186, 150, 135, 144, 179, 120, 112, 227, 241, 243, 244, 225, 166, 255, 148, 234, 246, 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