← previous blocknext block →recent activity
Analyzing
Block #83,398,597
9 transactions · 7 stateful · 2026-06-24 14:01:52 UTC
Parallelism
56/100
Blocked
43%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,398,597 · 9 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
1w02w16w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x4ed3af20…d87d
0x34b655…2a6f
4 touches
1 conflict
0x0835adb5…ad83
0x34b655…2a6f
4 touches
1 conflict
0x758bd24b…cc0c
0x34b655…2a6f
3 touches
1 conflict
0x4687571a…7681
0x34b655…2a6f
2 touches
0 conflicts
0x651411c9…66a9
0x34b655…2a6f
2 touches
0 conflicts
0x785889c9…0603
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity