← previous blocknext block →recent activity
Analyzing
Block #91,283,781
8 transactions · 7 stateful · 2026-07-29 07:26:24 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,283,781 · 8 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
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f63d67…5ba0
0x34b655…2a6f
4 touches
1 conflict
0x231ccc13…a7c6
0x34b655…2a6f
4 touches
1 conflict
0x33dde6d3…c08b
0x34b655…2a6f
4 touches
1 conflict
0x2fd12b6c…02cc
0x34b655…2a6f
2 touches
0 conflicts
0x3c1cd3a5…4b3e
0x34b655…2a6f
2 touches
0 conflicts
0x4a9804e7…2643
0x34b655…2a6f
2 touches
0 conflicts
0x64581fc5…7ecf
0x34b655…2a6f
2 touches
0 conflicts
0x6a87a861…e3e9
0x34b655…2a6f
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 0x60f63d6751…de5ba0
Audit this contract →
← previous block·next block →recent activity