Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b242c177cccc8b6862edb61fa6f9374c03adba4b6228418172be552e36ea6b30

Tx prefix hash: 0a9d47a1ed904a34c427e5d6b7bf67aa690632a2a8579c38a548b8f3544913e2
Tx public key: 4ead9e4cf460d8fd4e7b16cc29b82261f1fcd17d57bd4fbf6102752ce2e6a39a
Timestamp: 1679849607 Timestamp [UCT]: 2023-03-26 16:53:27 Age [y:d:h:m:s]: 01:336:22:07:01
Block: 725587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501426 RingCT/type: yes/0
Extra: 014ead9e4cf460d8fd4e7b16cc29b82261f1fcd17d57bd4fbf6102752ce2e6a39a0211000000035029cbac000000000000000000

1 output(s) for total of 2.420075635000 dcy

stealth address amount amount idx
00: 3a9b83d3a94cc3634bb457e46de2ccb46d519d5c42bfd36ecc9dba940ec5b801 2.420075635000 1170724 of 0

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": 725597, "vin": [ { "gen": { "height": 725587 } } ], "vout": [ { "amount": 2420075635, "target": { "key": "3a9b83d3a94cc3634bb457e46de2ccb46d519d5c42bfd36ecc9dba940ec5b801" } } ], "extra": [ 1, 78, 173, 158, 76, 244, 96, 216, 253, 78, 123, 22, 204, 41, 184, 34, 97, 241, 252, 209, 125, 87, 189, 79, 191, 97, 2, 117, 44, 226, 230, 163, 154, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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