← previous blocknext block →recent activity
Analyzing
Block #91,768,568
24 transactions · 14 stateful · 2026-07-31 00:06:39 UTC
Parallelism
88/100
Blocked
43%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,768,568 · 24 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
1w05w19w010w011w113w115w219w222w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3439dfbc…0d03
0x34b655…2a6f
6 touches
3 conflicts
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x00ddbbf2…4588
0x34b655…2a6f
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x0a51d6fa…1ea1
0x34b655…2a6f
4 touches
1 conflict
0x2e153698…5b40
0x34b655…2a6f
4 touches
1 conflict
0xf6322736…e546
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
3 conflicts on slot 0x3439dfbcc6…080d03
Audit this contract →
← previous block·next block →recent activity