← previous blocknext block →recent activity
Analyzing
Block #106,420,463
37 transactions · 35 stateful · 2026-09-20 08:53:09 UTC
Parallelism
57/100
Blocked
54%
Avg conflicts / tx
2.7
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,420,463 · 37 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w17w210w217w318w420w521w622w723w824w925w1026w1127w1028w1229w1330w1431w1536w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe9d1d23…3de2
0x34b655…2a6f
16 touches
28 conflicts
0x5e1c23e9…4f81
0x34b655…2a6f
14 touches
21 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
14 touches
21 conflicts
0xa8a44b97…b097
0x34b655…2a6f
12 touches
15 conflicts
0x310a7246…2dcb
0x34b655…2a6f
12 touches
15 conflicts
0x558eafff…804d
0x34b655…2a6f
12 touches
15 conflicts
0x810a3aa2…0227
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
12 touches
15 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
28 conflicts on slot 0xbe9d1d2362…0d3de2
Audit this contract →
← previous block·next block →recent activity