← previous blocknext block →recent activity
Analyzing
Block #99,485,212
19 transactions · 16 stateful · 2026-08-27 01:35:18 UTC
Parallelism
84/100
Blocked
19%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,485,212 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w011w012w014w115w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35d
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3d8de2eb…3199
0x34b655…2a6f
2 touches
0 conflicts
0x43eeb6cb…aca3
0x34b655…2a6f
2 touches
0 conflicts
0x593cce97…57ff
0x34b655…2a6f
2 touches
0 conflicts
0x5f9ed2e5…0f88
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
3 conflicts on slot 0x261cbea79d…12e35d
Audit this contract →
← previous block·next block →recent activity