← previous blocknext block →recent activity
Analyzing
Block #92,534,756
8 transactions · 7 stateful · 2026-08-02 16:20:22 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,534,756 · 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
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe26c4e53…94c3
0x34b655…2a6f
4 touches
1 conflict
0xfc4347fa…8f41
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x4fb86cd0…c67b
0x34b655…2a6f
4 touches
1 conflict
0x4fb86cd0…c67c
0x34b655…2a6f
4 touches
1 conflict
0x5649379f…d9eb
0x34b655…2a6f
4 touches
1 conflict
0x5e716a03…4096
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
1 conflict on slot 0xe26c4e5300…fb94c3
Audit this contract →
← previous block·next block →recent activity