← previous blocknext block →recent activity
Analyzing
Block #99,087,052
19 transactions · 15 stateful · 2026-08-25 16:11:09 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,087,052 · 19 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
1w07w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xca3ccf9e…6d2c
0xd32edf…ff58
3 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x3d1a888b…ba9d
0x34b655…2a6f
2 touches
0 conflicts
0xaa76c9db…4925
0x34b655…2a6f
2 touches
0 conflicts
0xab60dc09…85e4
0x34b655…2a6f
2 touches
0 conflicts
0xb550abea…2729
0x34b655…2a6f
2 touches
0 conflicts
0xbde524f4…43bf
0x34b655…2a6f
2 touches
0 conflicts
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity