← previous blocknext block →recent activity
Analyzing
Block #105,633,174
41 transactions · 36 stateful · 2026-09-17 14:48:21 UTC
Parallelism
81/100
Blocked
58%
Avg conflicts / tx
1.37
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,633,174 · 41 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w08w19w010w428w633w635w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x615bc8cc…15d2
0x34b655…2a6f
14 touches
21 conflicts
0xf61fea0c…4532
0x34b655…2a6f
12 touches
15 conflicts
0x9210e826…1414
0x34b655…2a6f
10 touches
10 conflicts
0xba1edffb…323e
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x0b7e340e…cbfc
0x34b655…2a6f
6 touches
3 conflicts
0xc09c3422…3c8b
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x615bc8cc79…5215d2
Audit this contract →
← previous block·next block →recent activity