← previous blocknext block →recent activity
Analyzing
Block #99,205,058
19 transactions · 17 stateful · 2026-08-26 02:05:01 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
0.74
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,205,058 · 19 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
1w02w03w16w07w08w110w112w213w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb276222e…49c7
0x34b655…2a6f
6 touches
3 conflicts
0x6ecd29e7…e900
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4786839b…c29a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x631b4113…baa9
0x34b655…2a6f
4 touches
1 conflict
0x72083f0d…082a
0x34b655…2a6f
4 touches
1 conflict
0xafc3a21b…d25a
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
3 conflicts on slot 0xb276222e05…fb49c7
Audit this contract →
← previous block·next block →recent activity