← previous blocknext block →recent activity
Analyzing
Block #99,184,294
30 transactions · 27 stateful · 2026-08-26 00:20:33 UTC
Parallelism
77/100
Blocked
48%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,184,294 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w19w010w111w012w015w116w018w219w220w323w324w425w226w328w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f7214d…8ec6
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xcec07536…c1a5
0x34b655…2a6f
6 touches
3 conflicts
0x9482a067…eba9
0x34b655…2a6f
6 touches
3 conflicts
0x053c3340…2135
0x34b655…2a6f
6 touches
3 conflicts
0x1fb6e47f…b99a
0x34b655…2a6f
6 touches
3 conflicts
0xfcd5e68f…2a12
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
6 conflicts on slot 0x53f7214d0d…cc8ec6
Audit this contract →
← previous block·next block →recent activity