← previous blocknext block →recent activity
Analyzing
Block #106,337,673
19 transactions · 19 stateful · 2026-09-20 01:56:30 UTC
Parallelism
68/100
Blocked
32%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,337,673 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w312w314w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6d87ec7…42eb
0x34b655…2a6f
10 touches
10 conflicts
0x735a86cd…b64d
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6c8f55db…27b0
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x261261a7…616f
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0xf6d87ec76c…cd42eb
Audit this contract →
← previous block·next block →recent activity