← previous blocknext block →recent activity
Analyzing
Block #91,189,947
14 transactions · 13 stateful · 2026-07-28 23:33:31 UTC
Parallelism
57/100
Blocked
46%
Avg conflicts / tx
1.07
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,189,947 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w27w39w412w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xbc66586e…20fe
0x34b655…2a6f
8 touches
6 conflicts
0xb75406fd…9760
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x7ef4ba09…2a25
0x34b655…2a6f
6 touches
3 conflicts
0xf1f725b1…d497
0x34b655…2a6f
6 touches
3 conflicts
0x4abaedb1…65b9
0x34b655…2a6f
6 touches
3 conflicts
0x67b966d6…9696
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity