← previous blocknext block →recent activity
Analyzing
Block #99,112,511
22 transactions · 19 stateful · 2026-08-25 18:19:19 UTC
Parallelism
91/100
Blocked
16%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,112,511 · 22 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
1w02w15w016w020w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xa02838a3…bc54
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xdef82efd…4584
0x34b655…2a6f
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0xc4e0b8c1…5070
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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 0x261cbea79d…12e35e
Audit this contract →
← previous block·next block →recent activity