← previous blocknext block →recent activity
Analyzing
Block #106,916,626
19 transactions · 18 stateful · 2026-09-22 02:31:25 UTC
Parallelism
84/100
Blocked
17%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,916,626 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w012w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb50ef533…79e4
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x469dac8d…3411
0x34b655…2a6f
4 touches
1 conflict
0x46cbc06b…eb46
0x34b655…2a6f
4 touches
1 conflict
0x593f95a5…b6e0
0x34b655…2a6f
4 touches
1 conflict
0x85bfd0af…ce96
0x34b655…2a6f
4 touches
1 conflict
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
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
1 conflict on slot 0xb50ef53385…9579e4
Audit this contract →
← previous block·next block →recent activity