← previous blocknext block →recent activity
Analyzing
Block #83,641,918
22 transactions · 17 stateful · 2026-06-25 17:05:58 UTC
Parallelism
86/100
Blocked
41%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,641,918 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w09w110w011w115w017w218w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0xfe92ad57…d1a1
0x34b655…2a6f
6 touches
3 conflicts
0x8ae827f1…aa36
0x34b655…2a6f
6 touches
3 conflicts
0x6767aeb1…eabc
0x34b655…2a6f
4 touches
1 conflict
0x7c93b38a…9e69
0x34b655…2a6f
4 touches
1 conflict
0xa1e51cc8…e4cf
0x34b655…2a6f
4 touches
1 conflict
0xa1eb8469…d895
0x34b655…2a6f
4 touches
1 conflict
0xbd68c7c7…40b3
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: 0x681e908b…e1ae09
3 conflicts on slot 0x0d622e34f9…000000
Audit this contract →
← previous block·next block →recent activity