← previous blocknext block →recent activity
Analyzing
Block #99,988,568
23 transactions · 19 stateful · 2026-08-28 20:02:50 UTC
Parallelism
74/100
Blocked
37%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,988,568 · 23 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
1w02w03w14w05w16w012w213w314w415w519w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e3014f0…b4e1
0x34b655…2a6f
10 touches
10 conflicts
0xdec5c2cc…c6ba
0x34b655…2a6f
10 touches
10 conflicts
0xfb14d7f1…e509
0x34b655…2a6f
8 touches
6 conflicts
0x5060cdde…445d
0x34b655…2a6f
6 touches
3 conflicts
0xc20bb30f…7331
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
10 conflicts on slot 0x5e3014f0c7…b1b4e1
Audit this contract →
← previous block·next block →recent activity