← previous blocknext block →recent activity
Analyzing
Block #92,325,118
13 transactions · 11 stateful · 2026-08-01 22:46:03 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,325,118 · 13 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
2w03w15w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa60eabc0…9f8c
0x34b655…2a6f
4 touches
1 conflict
0xc3f40a6f…f9b2
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xbb84f537…c9b2
0x34b655…2a6f
4 touches
1 conflict
0x478851bc…7631
0x34b655…2a6f
2 touches
0 conflicts
0x5947e5b2…3625
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 0xa60eabc0f8…119f8c
Audit this contract →
← previous block·next block →recent activity