← previous blocknext block →recent activity
Analyzing
Block #91,292,456
8 transactions · 8 stateful · 2026-07-29 08:10:04 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,292,456 · 8 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
2w03w14w26w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe85638e6…207a
0x34b655…2a6f
4 touches
1 conflict
0xf28a9fc2…05e4
0x34b655…2a6f
4 touches
1 conflict
0x13448752…c81a
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x204ded5c…4d7b
0x34b655…2a6f
2 touches
0 conflicts
0x20f13ae0…cca8
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 0xe85638e649…f9207a
Audit this contract →
← previous block·next block →recent activity