← previous blocknext block →recent activity
Analyzing
Block #106,282,798
24 transactions · 20 stateful · 2026-09-19 21:20:22 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,282,798 · 24 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
4w05w16w27w38w09w110w211w012w418w520w321w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x885efce3…7496
0x34b655…2a6f
10 touches
10 conflicts
0x93df16f9…095d
0x34b655…2a6f
8 touches
6 conflicts
0xa7011891…3437
0xd32edf…ff58
7 touches
6 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
6 touches
3 conflicts
0xe098738f…9bbe
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x5c3ecb74…af1d
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
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
10 conflicts on slot 0x885efce3b0…367496
Audit this contract →
← previous block·next block →recent activity