Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e8a3df99c94b7e416d07dea2ced2ff29254ca33481e66baecfa70bb649ea3f6

Tx prefix hash: 63fb78016943997711314ee00cab5ade55a3b7e2f5ed9c8892bb92fc7d49184b
Tx public key: 796d474837f471fdf83f8b5c0f1efa12c5e8a3a5ccad27341bc39a8ee04dfd61
Timestamp: 1754463364 Timestamp [UCT]: 2025-08-06 06:56:04 Age [y:d:h:m:s]: 00:055:12:21:44
Block: 1341305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38609 RingCT/type: yes/0
Extra: 01796d474837f471fdf83f8b5c0f1efa12c5e8a3a5ccad27341bc39a8ee04dfd61021100000003ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffcd0ab323461742ddb9892934480628e2086ffba4a346e190ceed09fc9229fd 0.600000000000 1829128 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": 1341315, "vin": [ { "gen": { "height": 1341305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffcd0ab323461742ddb9892934480628e2086ffba4a346e190ceed09fc9229fd" } } ], "extra": [ 1, 121, 109, 71, 72, 55, 244, 113, 253, 248, 63, 139, 92, 15, 30, 250, 18, 197, 232, 163, 165, 204, 173, 39, 52, 27, 195, 154, 142, 224, 77, 253, 97, 2, 17, 0, 0, 0, 3, 173, 121, 72, 208, 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