Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bb353cf9968a6f92e78a6a6a07d3f24f3b3f54273e43e154d056cb98a29844f

Tx prefix hash: 21af08ed3372356a6c33bf6b56764198cb4e6e3cd388ebba9ef02621686cc779
Tx public key: 7e390b3f3544e871c2ba56a6f1f3342fc943f3239a2a22f3e16bd87b27825a45
Timestamp: 1759019956 Timestamp [UCT]: 2025-09-28 00:39:16 Age [y:d:h:m:s]: 00:009:22:08:33
Block: 1377926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7103 RingCT/type: yes/0
Extra: 017e390b3f3544e871c2ba56a6f1f3342fc943f3239a2a22f3e16bd87b27825a4502110000000597baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c019956ce8f2293369e3958c8fda43b1bab2b9d133bb4f7e972a944e3dbdc35f 0.600000000000 1866021 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": 1377936, "vin": [ { "gen": { "height": 1377926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c019956ce8f2293369e3958c8fda43b1bab2b9d133bb4f7e972a944e3dbdc35f" } } ], "extra": [ 1, 126, 57, 11, 63, 53, 68, 232, 113, 194, 186, 86, 166, 241, 243, 52, 47, 201, 67, 243, 35, 154, 42, 34, 243, 225, 107, 216, 123, 39, 130, 90, 69, 2, 17, 0, 0, 0, 5, 151, 186, 249, 34, 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