← previous blocknext block →recent activity
Analyzing
Block #106,308,448
17 transactions · 16 stateful · 2026-09-19 23:29:26 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
1.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,308,448 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w15w28w09w110w212w313w416w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba65d335…5a78
0x34b655…2a6f
10 touches
10 conflicts
0x0fc536fb…1aa1
0x34b655…2a6f
8 touches
6 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
6 touches
3 conflicts
0x4be9812b…48a9
0x34b655…2a6f
6 touches
3 conflicts
0xc3c0295b…86a9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x07c47b1c…93c8
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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 0xba65d335ca…2c5a78
Audit this contract →
← previous block·next block →recent activity