← previous blocknext block →recent activity
Analyzing
Block #106,099,860
19 transactions · 16 stateful · 2026-09-19 05:59:37 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,099,860 · 19 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
1w02w14w09w110w111w212w313w314w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed506426…e6ad
0x34b655…2a6f
12 touches
15 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
8 touches
6 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
8 touches
6 conflicts
0xdc90bed5…58a9
0x34b655…2a6f
6 touches
3 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
6 touches
3 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8ba71bc5…c20b
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
15 conflicts on slot 0xed506426bf…a1e6ad
Audit this contract →
← previous block·next block →recent activity