← previous blocknext block →recent activity
Analyzing
Block #106,235,080
27 transactions · 27 stateful · 2026-09-19 17:20:14 UTC
Parallelism
56/100
Blocked
70%
Avg conflicts / tx
2.44
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,235,080 · 27 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w39w410w211w312w414w515w616w717w818w819w920w1021w1126w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde1dc398…c78f
0x34b655…2a6f
16 touches
28 conflicts
0xf00e711b…c539
0x34b655…2a6f
16 touches
28 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
12 touches
15 conflicts
0x83ff24ea…05f8
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0xde1dc39857…d1c78f
Audit this contract →
← previous block·next block →recent activity