← previous blocknext block →recent activity
Analyzing
Block #92,272,945
11 transactions · 9 stateful · 2026-08-01 18:23:40 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,272,945 · 11 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
1w02w14w06w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6baac03…62ca
0x34b655…2a6f
4 touches
1 conflict
0xe7bcaa18…161e
0x34b655…2a6f
4 touches
1 conflict
0xe8377f79…5f5e
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x31519d10…f76b
0x34b655…2a6f
4 touches
1 conflict
0x417b5b15…8f78
0x34b655…2a6f
4 touches
1 conflict
0x4952412a…362f
0x34b655…2a6f
4 touches
1 conflict
0x4ff5ffda…05aa
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 0xf6baac0300…df62ca
Audit this contract →
← previous block·next block →recent activity