Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 840b89214d782bbc2990a1362f190676b68b7b79662bc9c705b5d10b5b5371e8

Tx prefix hash: e98e97a8c4373965937f191bd003923d00bef03ec02ff7e45a085b8bc1619e76
Tx public key: 2179f7a6567802d92d92cc6a806f717145db5d8641fdc865ebed2238be8b07c9
Timestamp: 1764998562 Timestamp [UCT]: 2025-12-06 05:22:42 Age [y:d:h:m:s]: 00:058:08:50:11
Block: 1427471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41635 RingCT/type: yes/0
Extra: 012179f7a6567802d92d92cc6a806f717145db5d8641fdc865ebed2238be8b07c9021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb31378156f668c19c86a5332aa4c7e7b42170c27fd4de7c7e0c76b6fe9bf5bc 0.600000000000 1916172 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": 1427481, "vin": [ { "gen": { "height": 1427471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb31378156f668c19c86a5332aa4c7e7b42170c27fd4de7c7e0c76b6fe9bf5bc" } } ], "extra": [ 1, 33, 121, 247, 166, 86, 120, 2, 217, 45, 146, 204, 106, 128, 111, 113, 113, 69, 219, 93, 134, 65, 253, 200, 101, 235, 237, 34, 56, 190, 139, 7, 201, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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