← previous blocknext block →recent activity
Analyzing
Block #106,385,931
25 transactions · 25 stateful · 2026-09-20 05:59:23 UTC
Parallelism
72/100
Blocked
28%
Avg conflicts / tx
0.8
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,385,931 · 25 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
6w07w18w29w310w411w512w623w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40c584a0…3f07
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0xb6fcbbb7…2b31
0x34b655…2a6f
10 touches
10 conflicts
0x51d607f1…6458
0x34b655…2a6f
10 touches
10 conflicts
0x961c0cd9…0937
0x34b655…2a6f
8 touches
6 conflicts
0xac0b4a08…faae
0x34b655…2a6f
8 touches
6 conflicts
0x78f0df52…656d
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
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
15 conflicts on slot 0x40c584a0fc…ad3f07
Audit this contract →
← previous block·next block →recent activity