← previous blocknext block →recent activity
Analyzing
Block #106,376,704
22 transactions · 20 stateful · 2026-09-20 05:12:56 UTC
Parallelism
68/100
Blocked
45%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,376,704 · 22 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
1w02w17w210w012w314w416w117w518w019w620w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19f59494…c7f1
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x7cbbdd3f…65b0
0x34b655…2a6f
6 touches
3 conflicts
0x17bb579f…938c
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x316e0cce…22ee
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7462b8f2…6312
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 0x19f594940e…78c7f1
Audit this contract →
← previous block·next block →recent activity