← previous blocknext block →recent activity
Analyzing
Block #83,693,642
15 transactions · 14 stateful · 2026-06-25 22:51:01 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.87
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,693,642 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w07w28w313w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8fec9ca…2d60
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x0ad4dbe8…ae93
0x34b655…2a6f
4 touches
1 conflict
0x0e6835c8…1f17
0x34b655…2a6f
4 touches
1 conflict
0x1175233a…64e7
0x34b655…2a6f
4 touches
1 conflict
0x213a54fa…c85f
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0xc8fec9cacc…f42d60
Audit this contract →
← previous block·next block →recent activity