← previous blocknext block →recent activity
Analyzing
Block #106,039,095
38 transactions · 35 stateful · 2026-09-19 00:53:49 UTC
Parallelism
82/100
Blocked
46%
Avg conflicts / tx
0.87
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,039,095 · 38 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
2w03w06w07w08w19w010w111w212w013w114w219w120w121w122w223w324w226w229w333w437w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7cf3eb0f…06c5
0x34b655…2a6f
6 touches
3 conflicts
0x94dabb65…43a3
0x34b655…2a6f
6 touches
3 conflicts
0xf0d81f74…f079
0x34b655…2a6f
4 touches
1 conflict
0x4d86f36a…481c
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity