← previous blocknext block →recent activity
Analyzing
Block #99,502,111
26 transactions · 23 stateful · 2026-08-27 03:00:22 UTC
Parallelism
81/100
Blocked
52%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,502,111 · 26 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
1w03w04w15w07w19w010w113w215w216w118w219w320w421w224w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xea57afd0…4232
0x34b655…2a6f
6 touches
3 conflicts
0x3e49348b…9445
0x34b655…2a6f
4 touches
1 conflict
0x4c574adc…611d
0x34b655…2a6f
4 touches
1 conflict
0x4f63dad0…0d10
0x34b655…2a6f
4 touches
1 conflict
0xc46fc833…17fe
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity