← previous blocknext block →recent activity
Analyzing
Block #99,586,657
18 transactions · 18 stateful · 2026-08-27 10:08:47 UTC
Parallelism
83/100
Blocked
28%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,586,657 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w18w112w116w017w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffebc308…5fd9
0x34b655…2a6f
4 touches
1 conflict
0x1031484e…d248
0x34b655…2a6f
4 touches
1 conflict
0x256341f6…89e9
0x34b655…2a6f
4 touches
1 conflict
0x2caeb7f5…b6bb
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x705ab4ae…0162
0x34b655…2a6f
4 touches
1 conflict
0x8b780b26…f5ff
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
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
1 conflict on slot 0xffebc308a9…8e5fd9
Audit this contract →
← previous block·next block →recent activity