← previous blocknext block →recent activity
Analyzing
Block #93,843,878
18 transactions · 17 stateful · 2026-08-07 06:06:19 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,843,878 · 18 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
1w02w14w05w17w08w113w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2328941c…84d3
0x34b655…2a6f
6 touches
3 conflicts
0xeb0f666f…02d5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x6129fdf9…1a84
0xd32edf…ff58
3 touches
1 conflict
0x06e40499…165e
0x2b46c0…1669
2 touches
0 conflicts
0xa605468c…1bfc
0x2b46c0…1669
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
3 conflicts on slot 0x2328941c9c…fc84d3
Audit this contract →
← previous block·next block →recent activity