← previous blocknext block →recent activity
Analyzing
Block #106,381,734
24 transactions · 22 stateful · 2026-09-20 05:38:15 UTC
Parallelism
54/100
Blocked
55%
Avg conflicts / tx
2
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,381,734 · 24 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w19w210w312w113w414w515w616w717w818w919w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ecffdb2…0a01
0x34b655…2a6f
18 touches
36 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
16 touches
28 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
10 touches
10 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
10 touches
10 conflicts
0x4984f7be…d515
0x34b655…2a6f
10 touches
10 conflicts
0x1dc299dc…1b73
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x78c87345…4d2c
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
36 conflicts on slot 0x2ecffdb210…300a01
Audit this contract →
← previous block·next block →recent activity