Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7f60a7759352f5e0693826a3f888716ca21f5d0e9fe12f1cd83dd28ea59746d

Tx prefix hash: f7c42b7ae5294f8101d3cd3ade13c0a667b62f418b4f9f6806e3a19fcac189cb
Tx public key: c904a6f50e6a51b09993f48f95fab9e1529ed656b52a73bcfc7c04aa2a712f1b
Timestamp: 1724860786 Timestamp [UCT]: 2024-08-28 15:59:46 Age [y:d:h:m:s]: 01:063:15:33:43
Block: 1097850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303935 RingCT/type: yes/0
Extra: 01c904a6f50e6a51b09993f48f95fab9e1529ed656b52a73bcfc7c04aa2a712f1b021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 125e684f50201f24d46c9c64544509f83b5c22aafb77010c946dac0c8dc40854 0.600000000000 1573361 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": 1097860, "vin": [ { "gen": { "height": 1097850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "125e684f50201f24d46c9c64544509f83b5c22aafb77010c946dac0c8dc40854" } } ], "extra": [ 1, 201, 4, 166, 245, 14, 106, 81, 176, 153, 147, 244, 143, 149, 250, 185, 225, 82, 158, 214, 86, 181, 42, 115, 188, 252, 124, 4, 170, 42, 113, 47, 27, 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