Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1fe51811c98dd8f1912d9427e12aaa684cd43b81f17288ce52ded924635ac39

Tx prefix hash: e4c7cdd7643d52cfb615524f1b4714e752e60e5810ba4999ee7dfa458db840b2
Tx public key: 2e1e63ea058006961fcdb8906803ea9c25cb825dede5ace4d3036ccf945d4b99
Timestamp: 1762586776 Timestamp [UCT]: 2025-11-08 07:26:16 Age [y:d:h:m:s]: 00:060:08:38:04
Block: 1407490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43234 RingCT/type: yes/0
Extra: 012e1e63ea058006961fcdb8906803ea9c25cb825dede5ace4d3036ccf945d4b990211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc43b2c41b6ffeb5660ec2d6adea8a8c1c4e2cdacac07df82ae7001ab87be57e 0.600000000000 1895911 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": 1407500, "vin": [ { "gen": { "height": 1407490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc43b2c41b6ffeb5660ec2d6adea8a8c1c4e2cdacac07df82ae7001ab87be57e" } } ], "extra": [ 1, 46, 30, 99, 234, 5, 128, 6, 150, 31, 205, 184, 144, 104, 3, 234, 156, 37, 203, 130, 93, 237, 229, 172, 228, 211, 3, 108, 207, 148, 93, 75, 153, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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