← previous blocknext block →recent activity
Analyzing
Block #106,554,421
146 transactions · 80 stateful · 2026-09-20 20:07:24 UTC
Parallelism
89/100
Blocked
74%
Avg conflicts / tx
2.32
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,554,421 · 146 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
2w05w18w09w010w118w219w327w428w529w630w731w832w935w1037w438w539w643w644w564w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
30 touches
105 conflicts
0xa846479e…5e63
0xd32edf…ff58
25 touches
78 conflicts
0xea02471d…1542
0x34b655…2a6f
22 touches
55 conflicts
0xaad6be10…0801
0x2a68ba…90c5
20 touches
45 conflicts
0x00000000…003d
0x065c9d…c394
18 touches
36 conflicts
0xcc8faac2…c766
0x065c9d…c394
18 touches
36 conflicts
0xf3d10975…0d07
0x34b655…2a6f
18 touches
36 conflicts
0x18cf3003…51d1
0x065c9d…c394
16 touches
28 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
105 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity