← previous blocknext block →recent activity
Analyzing
Block #106,188,126
31 transactions · 29 stateful · 2026-09-19 13:23:49 UTC
Parallelism
61/100
Blocked
69%
Avg conflicts / tx
2.1
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,188,126 · 31 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
1w02w13w24w35w06w17w28w312w415w218w319w420w521w622w723w824w925w1026w1129w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a29c64d…e772
0x34b655…2a6f
14 touches
21 conflicts
0x72d35c7e…525e
0x34b655…2a6f
12 touches
15 conflicts
0xd41f5136…97c6
0x34b655…2a6f
12 touches
15 conflicts
0x76ed8777…1e5f
0x34b655…2a6f
10 touches
10 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
10 touches
10 conflicts
0xba5743c7…21c5
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x1b25f260…c429
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
21 conflicts on slot 0x1a29c64dd8…e6e772
Audit this contract →
← previous block·next block →recent activity