← previous blocknext block →recent activity
Analyzing
Block #99,239,927
13 transactions · 12 stateful · 2026-08-26 05:00:28 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,239,927 · 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
1w03w110w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4c9b009…58f1
0x34b655…2a6f
4 touches
1 conflict
0xfe45073e…6315
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x551057cd…3c97
0x065c9d…c394
2 touches
0 conflicts
0xc4279746…8290
0x065c9d…c394
2 touches
0 conflicts
0xd19fd35e…0d1f
0x065c9d…c394
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 0xb4c9b009e6…a658f1
Audit this contract →
← previous block·next block →recent activity