← previous blocknext block →recent activity
Analyzing
Block #92,272,501
16 transactions · 15 stateful · 2026-08-01 18:21:26 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,272,501 · 16 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
1w02w16w07w011w012w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b19d990…5f3a
0x34b655…2a6f
4 touches
1 conflict
0x1b8f048a…581d
0x34b655…2a6f
4 touches
1 conflict
0x326f2a00…a2a6
0x34b655…2a6f
4 touches
1 conflict
0x410b84ab…1dbc
0x34b655…2a6f
4 touches
1 conflict
0x4bf59d22…00de
0x34b655…2a6f
4 touches
1 conflict
0x4ff5ffda…05aa
0x34b655…2a6f
4 touches
1 conflict
0x5bb46f6c…7693
0x34b655…2a6f
4 touches
1 conflict
0x70b5d52d…3ea7
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 0x0b19d99072…ba5f3a
Audit this contract →
← previous block·next block →recent activity