← previous blocknext block →recent activity
Analyzing
Block #106,186,244
15 transactions · 14 stateful · 2026-09-19 13:14:21 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,186,244 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w011w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xfc2e5e93…b608
0x34b655…2a6f
4 touches
1 conflict
0x21e79ad8…c5db
0x34b655…2a6f
4 touches
1 conflict
0x6ea13ae5…72d1
0x34b655…2a6f
3 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
2 touches
0 conflicts
0x08de772c…8e84
0x2a68ba…90c5
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x8b87ece6…3353
0x34b655…2a6f
2 touches
0 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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity