← previous blocknext block →recent activity
Analyzing
Block #92,189,901
11 transactions · 10 stateful · 2026-08-01 11:26:00 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,189,901 · 11 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
2w03w14w25w39w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c0e32fc…a6ca
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x152f8e3d…3da0
0x34b655…2a6f
4 touches
1 conflict
0x30ae635d…5e67
0x34b655…2a6f
4 touches
1 conflict
0x32b804b3…ce18
0x34b655…2a6f
4 touches
1 conflict
0x34b6e036…2161
0x34b655…2a6f
4 touches
1 conflict
0x44df3c2a…bafe
0x34b655…2a6f
4 touches
1 conflict
0x44df3c2a…baff
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 0x6c0e32fc91…09a6ca
Audit this contract →
← previous block·next block →recent activity