← previous blocknext block →recent activity
Analyzing
Block #99,196,737
22 transactions · 21 stateful · 2026-08-26 01:23:10 UTC
Parallelism
73/100
Blocked
52%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,196,737 · 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
1w03w15w07w19w210w211w312w414w315w416w517w220w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd92e861b…f3d5
0x34b655…2a6f
12 touches
15 conflicts
0x961c0cd9…0937
0x34b655…2a6f
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x348fda08…7e96
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xb54c8ced…5b8c
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
15 conflicts on slot 0xd92e861bb1…6df3d5
Audit this contract →
← previous block·next block →recent activity