← previous blocknext block →recent activity
Analyzing
Block #92,771,985
14 transactions · 12 stateful · 2026-08-03 12:14:43 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,771,985 · 14 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
2w08w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4658f5c…b257
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xb6ea4726…5140
0x34b655…2a6f
4 touches
1 conflict
0x03b39bca…ec51
0x34b655…2a6f
2 touches
0 conflicts
0x544474d6…71b4
0x34b655…2a6f
2 touches
0 conflicts
0x6f8644f7…10fa
0x34b655…2a6f
2 touches
0 conflicts
0x743061ce…a4ac
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 0xa4658f5c4c…e0b257
Audit this contract →
← previous block·next block →recent activity