← previous blocknext block →recent activity
Analyzing
Block #91,547,396
10 transactions · 9 stateful · 2026-07-30 05:34:05 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,547,396 · 10 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
1w03w15w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8433624…8969
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0x09cde4ee…e38c
0x34b655…2a6f
2 touches
0 conflicts
0x1ed748d8…d530
0x34b655…2a6f
2 touches
0 conflicts
0x47c46531…b91e
0x34b655…2a6f
2 touches
0 conflicts
0x4cb89fd4…9bb8
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 0xa843362480…528969
Audit this contract →
← previous block·next block →recent activity