Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8648a7780257a13ebef92ac79b0513a76bfb18f14ac8d4a87844116351423ef

Tx prefix hash: a9b09bbc753b5f58f1b37fdc2978601b415cec55416c9d90763b2d6e4a9cb4d9
Tx public key: c84311157985d5a2f5a2053011b84990db71226786083f7fb0980b46d442cdb0
Timestamp: 1726045474 Timestamp [UCT]: 2024-09-11 09:04:34 Age [y:d:h:m:s]: 00:119:20:19:48
Block: 1107672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85717 RingCT/type: yes/0
Extra: 01c84311157985d5a2f5a2053011b84990db71226786083f7fb0980b46d442cdb0021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7309c7c866af87a25d95f766d82717586e323fd1e122d06f0afb1aa4fa3d9d7e 0.600000000000 1585293 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": 1107682, "vin": [ { "gen": { "height": 1107672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7309c7c866af87a25d95f766d82717586e323fd1e122d06f0afb1aa4fa3d9d7e" } } ], "extra": [ 1, 200, 67, 17, 21, 121, 133, 213, 162, 245, 162, 5, 48, 17, 184, 73, 144, 219, 113, 34, 103, 134, 8, 63, 127, 176, 152, 11, 70, 212, 66, 205, 176, 2, 17, 0, 0, 0, 8, 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