← previous blocknext block →recent activity
Analyzing
Block #99,202,425
22 transactions · 22 stateful · 2026-08-26 01:51:47 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,202,425 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w110w211w012w213w314w415w517w118w321w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1856468…e84f
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0x9442eee9…a2a4
0x065c9d…c394
4 touches
1 conflict
0xdbd0009d…ac12
0x065c9d…c394
4 touches
1 conflict
0x5a27cf34…ae3b
0x34b655…2a6f
4 touches
1 conflict
0x7a78336e…dd1e
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
6 conflicts on slot 0xb185646883…2ae84f
Audit this contract →
← previous block·next block →recent activity