Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa3d804d2383bd8d04a0e3c349d2f30def55de0f9b44f86c8cd613d1591dd2cf

Tx prefix hash: b1e51d7a1b5cb7c671fa831b0d127568b6a114816a8ac98171c68a1fc2641ed6
Tx public key: d7b14868e4f70ee859e6c7450ed16ea2c1dd84b34be293bf1a57e75610428b83
Timestamp: 1759324229 Timestamp [UCT]: 2025-10-01 13:10:29 Age [y:d:h:m:s]: 00:088:05:44:11
Block: 1380456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63186 RingCT/type: yes/0
Extra: 01d7b14868e4f70ee859e6c7450ed16ea2c1dd84b34be293bf1a57e75610428b83021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc7dbef8accaff4fefeabbf4522c5a6f95cc0c16ee98146534ebdb7711591799 0.600000000000 1868567 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": 1380466, "vin": [ { "gen": { "height": 1380456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc7dbef8accaff4fefeabbf4522c5a6f95cc0c16ee98146534ebdb7711591799" } } ], "extra": [ 1, 215, 177, 72, 104, 228, 247, 14, 232, 89, 230, 199, 69, 14, 209, 110, 162, 193, 221, 132, 179, 75, 226, 147, 191, 26, 87, 231, 86, 16, 66, 139, 131, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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