Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d000ed1a5c9f7a23b5652cbc100de408074a84ee692614740bcf43078540d3d5

Tx prefix hash: 8e2753784881ea904526005c6dcc1f66fe68b8963ae4cbf35e74b0404a55a075
Tx public key: 0bf0576d7a4da35893ad2c3b672202b3efcde7ad6af58f79d66ccfd28c6ef9f0
Timestamp: 1763285541 Timestamp [UCT]: 2025-11-16 09:32:21 Age [y:d:h:m:s]: 00:012:00:33:41
Block: 1413287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8610 RingCT/type: yes/0
Extra: 010bf0576d7a4da35893ad2c3b672202b3efcde7ad6af58f79d66ccfd28c6ef9f002110000000217b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 561bc0ef49123d91a73f0dcdf4a55dd6e5b24c7f412baa4a6ae4c671f35a394f 0.600000000000 1901766 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": 1413297, "vin": [ { "gen": { "height": 1413287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "561bc0ef49123d91a73f0dcdf4a55dd6e5b24c7f412baa4a6ae4c671f35a394f" } } ], "extra": [ 1, 11, 240, 87, 109, 122, 77, 163, 88, 147, 173, 44, 59, 103, 34, 2, 179, 239, 205, 231, 173, 106, 245, 143, 121, 214, 108, 207, 210, 140, 110, 249, 240, 2, 17, 0, 0, 0, 2, 23, 177, 145, 50, 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