← previous blocknext block →recent activity
Analyzing
Block #92,190,153
8 transactions · 7 stateful · 2026-08-01 11:27:16 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,190,153 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2019d5b…0332
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x41d39318…d624
0x34b655…2a6f
4 touches
1 conflict
0x1af76d0b…efde
0x34b655…2a6f
2 touches
0 conflicts
0x1eb410fd…591d
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x24d238da…0c38
0x34b655…2a6f
2 touches
0 conflicts
0x2a0c0a9c…5ea2
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 0xc2019d5bf6…ff0332
Audit this contract →
← previous block·next block →recent activity