← previous blocknext block →recent activity
Analyzing
Block #91,087,196
6 transactions · 6 stateful · 2026-07-28 14:56:35 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,087,196 · 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
2w03w14w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x758f26d7…858f
0x01bff4…1071
2 touches
0 conflicts
0xa8e98b9f…5935
0x01bff4…1071
2 touches
0 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
2 touches
0 conflicts
0x0494220d…abf7
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 0xc824469a90…af6426
Audit this contract →
← previous block·next block →recent activity