← previous blocknext block →recent activity
Analyzing
Block #83,639,739
13 transactions · 13 stateful · 2026-06-25 16:51:26 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,639,739 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w09w111w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee7978e9…2869
0x34b655…2a6f
8 touches
6 conflicts
0x0d728315…9cf5
0x34b655…2a6f
8 touches
6 conflicts
0x37447887…710e
0x34b655…2a6f
6 touches
3 conflicts
0x403d1735…de44
0x34b655…2a6f
4 touches
1 conflict
0x431cda43…afe8
0x34b655…2a6f
4 touches
1 conflict
0x6e91214a…c666
0x34b655…2a6f
4 touches
1 conflict
0x6f58168d…ea24
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
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 0xee7978e97a…ed2869
Audit this contract →
← previous block·next block →recent activity