← previous blocknext block →recent activity
Analyzing
Block #91,402,754
21 transactions · 17 stateful · 2026-07-29 17:25:10 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,402,754 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w27w314w015w116w117w218w319w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2840c278…bbc7
0x34b655…2a6f
6 touches
3 conflicts
0x04e85631…60f8
0x34b655…2a6f
4 touches
1 conflict
0x05705e23…9806
0x34b655…2a6f
4 touches
1 conflict
0x312e7bb3…b9b4
0x34b655…2a6f
4 touches
1 conflict
0x36f93b7d…927a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x525cb249…2e98
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity