← previous blocknext block →recent activity
Analyzing
Block #92,221,837
13 transactions · 13 stateful · 2026-08-01 14:06:36 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,221,837 · 13 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
1w02w14w05w18w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc371f5e…0955
0x34b655…2a6f
4 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x62b13313…bbe8
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x8900cf87…5261
0x34b655…2a6f
4 touches
1 conflict
0x9cb562ca…5ae6
0x34b655…2a6f
4 touches
1 conflict
0xabdf81c9…b3b0
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: Perpl
1 conflict on slot 0xfc371f5ead…b30955
Audit this contract →
← previous block·next block →recent activity