Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3aebd7ee2dbe19924156d30c933dcb9d73ed300e56a1d224f7e9336cfb83a221

Tx prefix hash: c43ce7ada92f190ebcd05603c850c9d85676db26623adcada8a4b9d01f24b86f
Tx public key: 81f47e62bde380895c604b48261fb7fd13850c7415e3baa845d5ae247736c500
Timestamp: 1743320432 Timestamp [UCT]: 2025-03-30 07:40:32 Age [y:d:h:m:s]: 00:228:12:08:10
Block: 1250399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161039 RingCT/type: yes/0
Extra: 0181f47e62bde380895c604b48261fb7fd13850c7415e3baa845d5ae247736c5000211000000069ba629df000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f8e7d1fb20c6c67f56a80c9aa49ba7581281ce2e17e34b198265aa9ec0099b2 0.600000000000 1737448 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": 1250409, "vin": [ { "gen": { "height": 1250399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f8e7d1fb20c6c67f56a80c9aa49ba7581281ce2e17e34b198265aa9ec0099b2" } } ], "extra": [ 1, 129, 244, 126, 98, 189, 227, 128, 137, 92, 96, 75, 72, 38, 31, 183, 253, 19, 133, 12, 116, 21, 227, 186, 168, 69, 213, 174, 36, 119, 54, 197, 0, 2, 17, 0, 0, 0, 6, 155, 166, 41, 223, 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