← previous blocknext block →recent activity
Analyzing
Block #106,402,818
23 transactions · 20 stateful · 2026-09-20 07:24:21 UTC
Parallelism
70/100
Blocked
60%
Avg conflicts / tx
1.26
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,402,818 · 23 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
1w02w03w14w15w27w38w49w510w114w619w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd563f3a1…94b1
0x34b655…2a6f
6 touches
3 conflicts
0xc55f50c5…c7cf
0x5be4ee…673f
5 touches
3 conflicts
0xc55f50c5…c7dd
0x5be4ee…673f
5 touches
3 conflicts
0x502b3ee1…7f7c
0x34b655…2a6f
4 touches
1 conflict
0x7462b8f2…6312
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity