← previous blocknext block →recent activity
Analyzing
Block #99,195,981
20 transactions · 18 stateful · 2026-08-26 01:19:22 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,195,981 · 20 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
1w02w04w15w06w17w28w011w212w113w216w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x548ef1da…c736
0x34b655…2a6f
6 touches
3 conflicts
0xb1856468…e84f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xee0d9bf9…7dab
0x34b655…2a6f
6 touches
3 conflicts
0x47cdb5a5…6b93
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x48b13e5e…3c2a
0x34b655…2a6f
4 touches
1 conflict
0x55010ec8…ea31
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 0x548ef1dac4…ecc736
Audit this contract →
← previous block·next block →recent activity