← previous blocknext block →recent activity
Analyzing
Block #105,844,047
20 transactions · 20 stateful · 2026-09-18 08:31:05 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.55
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,844,047 · 20 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
1w02w13w07w18w09w111w212w213w314w415w516w619w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc40fa8a7…a319
0x34b655…2a6f
14 touches
21 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x5fad6fee…7714
0x34b655…2a6f
8 touches
6 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
8 touches
6 conflicts
0xf95156ea…854b
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x13ded4ac…f298
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
21 conflicts on slot 0xc40fa8a7a4…d2a319
Audit this contract →
← previous block·next block →recent activity