← previous blocknext block →recent activity
Analyzing
Block #91,438,441
6 transactions · 6 stateful · 2026-07-29 20:25:55 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,438,441 · 6 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcbe18c62…3a5c
0x34b655…2a6f
4 touches
1 conflict
0xfcc8f826…7c5f
0x34b655…2a6f
4 touches
1 conflict
0x1bd6ddeb…9a19
0x34b655…2a6f
4 touches
1 conflict
0x448a51f4…1a6d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x70bbe2cf…99f7
0x34b655…2a6f
4 touches
1 conflict
0x7c1dfb78…a4a0
0x34b655…2a6f
4 touches
1 conflict
0xc5a1b2fe…5369
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 0xcbe18c620b…303a5c
Audit this contract →
← previous block·next block →recent activity