← previous blocknext block →recent activity
Analyzing
Block #99,879,474
22 transactions · 19 stateful · 2026-08-28 10:53:05 UTC
Parallelism
77/100
Blocked
53%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,879,474 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w17w08w19w110w213w314w415w416w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70d81211…f49f
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x06e40499…165e
0x2b46c0…1669
4 touches
1 conflict
0xa605468c…1bfc
0x2b46c0…1669
4 touches
1 conflict
0x207e9f25…4724
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
6 conflicts on slot 0x70d812119d…c1f49f
Audit this contract →
← previous block·next block →recent activity