← previous blocknext block →recent activity
Analyzing
Block #91,422,472
8 transactions · 7 stateful · 2026-07-29 19:04:41 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,422,472 · 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
1w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e7de6d7…48be
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x05e1eba1…6491
0x34b655…2a6f
2 touches
0 conflicts
0x068d0c9f…81f4
0x34b655…2a6f
2 touches
0 conflicts
0x0a906ba5…2454
0x34b655…2a6f
2 touches
0 conflicts
0x1353affc…75e0
0x34b655…2a6f
2 touches
0 conflicts
0x189e374d…c093
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 0x7e7de6d71b…4948be
Audit this contract →
← previous block·next block →recent activity