← previous blocknext block →recent activity
Analyzing
Block #99,873,390
14 transactions · 14 stateful · 2026-08-28 10:22:25 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,873,390 · 14 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
1w02w17w09w111w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbad4e90b…33a5
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x5f0de5e9…535c
0x40c49f…2af0
4 touches
1 conflict
0x6648146b…0d86
0x40c49f…2af0
4 touches
1 conflict
0x0efc210e…70ab
0x34b655…2a6f
4 touches
1 conflict
0x4b9449ea…c5bf
0x34b655…2a6f
3 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 0xbad4e90ba6…2233a5
Audit this contract →
← previous block·next block →recent activity