← previous blocknext block →recent activity
Analyzing
Block #99,318,187
11 transactions · 11 stateful · 2026-08-26 11:34:13 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,318,187 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w39w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x310a7246…2dcb
0x34b655…2a6f
6 touches
3 conflicts
0x14342d23…ec84
0x34b655…2a6f
6 touches
3 conflicts
0x947bb79d…6458
0x34b655…2a6f
6 touches
3 conflicts
0xbf94be27…e9c5
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x81ca8c9e…28cb
0x34b655…2a6f
4 touches
1 conflict
0x932a9590…0b19
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
3 conflicts on slot 0x310a7246ab…012dcb
Audit this contract →
← previous block·next block →recent activity