Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99448cc9220b679f7d79f8936d8d3543c85e9f91f99dae4c596c22017b9e4ebb

Tx prefix hash: a68fd26a943d815e747125b18b7d7b6f7782be634c83a276b07e0a6e532e7349
Tx public key: f8186c5991fc55c822a9be3e769052d40879375a8eb8523e575fd63d75edc267
Timestamp: 1723710923 Timestamp [UCT]: 2024-08-15 08:35:23 Age [y:d:h:m:s]: 00:260:17:20:03
Block: 1088330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186221 RingCT/type: yes/0
Extra: 01f8186c5991fc55c822a9be3e769052d40879375a8eb8523e575fd63d75edc267021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf4533925f0bccad00f356f8965b84a2ab65a1a0c65c44db7dabad38cbffd8f1 0.600000000000 1562945 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": 1088340, "vin": [ { "gen": { "height": 1088330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf4533925f0bccad00f356f8965b84a2ab65a1a0c65c44db7dabad38cbffd8f1" } } ], "extra": [ 1, 248, 24, 108, 89, 145, 252, 85, 200, 34, 169, 190, 62, 118, 144, 82, 212, 8, 121, 55, 90, 142, 184, 82, 62, 87, 95, 214, 61, 117, 237, 194, 103, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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