← previous blocknext block →recent activity
Analyzing
Block #91,126,445
16 transactions · 15 stateful · 2026-07-28 18:14:04 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,126,445 · 16 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
2w05w06w111w112w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0x3d4a4a17…e015
0x34b655…2a6f
4 touches
1 conflict
0xa779293b…5e59
0x34b655…2a6f
4 touches
1 conflict
0xa98e6cb0…8051
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x152f8e3d…3da0
0x34b655…2a6f
4 touches
1 conflict
0x32e4c206…a476
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 0x206f43799d…55e08a
Audit this contract →
← previous block·next block →recent activity