← previous blocknext block →recent activity
Analyzing
Block #91,026,796
7 transactions · 5 stateful · 2026-07-28 09:52:40 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,026,796 · 7 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xddd7607e…9b4b
0x34b655…2a6f
4 touches
1 conflict
0x5fe7e126…6dd2
0x34b655…2a6f
4 touches
1 conflict
0xbf8a0690…c879
0x34b655…2a6f
4 touches
1 conflict
0x0e27f143…3ad0
0x065c9d…c394
2 touches
0 conflicts
0x32b186ef…2b94
0x065c9d…c394
2 touches
0 conflicts
0x37ec4b44…0cc2
0x065c9d…c394
2 touches
0 conflicts
0x55cde452…83ea
0x065c9d…c394
2 touches
0 conflicts
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity