← previous blocknext block →recent activity
Analyzing
Block #91,409,026
13 transactions · 12 stateful · 2026-07-29 17:56:56 UTC
Parallelism
62/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,409,026 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w17w28w09w111w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb874a6c…caa0
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc8722a8f…f98e
0x34b655…2a6f
6 touches
3 conflicts
0x5a812049…d85d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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
6 conflicts on slot 0xfb874a6c9f…bfcaa0
Audit this contract →
← previous block·next block →recent activity