← previous blocknext block →recent activity
Analyzing
Block #99,957,424
25 transactions · 19 stateful · 2026-08-28 17:25:55 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,957,424 · 25 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
1w02w14w05w16w27w314w215w417w019w220w122w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f54a736…3a3b
0x34b655…2a6f
10 touches
10 conflicts
0x88089e56…29f6
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb7ce83b1…2c96
0x34b655…2a6f
6 touches
3 conflicts
0x0cd55e93…bf0e
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xebe581d8…2696
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x0f54a73694…493a3b
Audit this contract →
← previous block·next block →recent activity