← previous blocknext block →recent activity
Analyzing
Block #106,422,458
25 transactions · 19 stateful · 2026-09-20 09:03:12 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,422,458 · 25 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
1w02w04w15w16w27w311w113w216w019w122w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd4e632c…e14c
0x34b655…2a6f
8 touches
6 conflicts
0x5f76b8ee…ecfe
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x74cdc294…26a8
0x34b655…2a6f
4 touches
1 conflict
0x88fc2a68…3918
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
6 conflicts on slot 0xfd4e632c76…e1e14c
Audit this contract →
← previous block·next block →recent activity