← previous blocknext block →recent activity
Analyzing
Block #106,453,105
34 transactions · 32 stateful · 2026-09-20 11:37:30 UTC
Parallelism
53/100
Blocked
69%
Avg conflicts / tx
3.26
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,453,105 · 34 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
1w02w03w04w15w110w011w112w213w314w115w416w517w618w719w820w921w1023w1125w126w1227w1328w1429w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89eaf36a…4e48
0x34b655…2a6f
24 touches
66 conflicts
0xe1944aff…428b
0x34b655…2a6f
16 touches
28 conflicts
0x80398c66…f3cc
0x34b655…2a6f
14 touches
21 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
14 touches
21 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
14 touches
21 conflicts
0x1b25f260…c429
0x34b655…2a6f
14 touches
21 conflicts
0xf217fa05…207f
0x34b655…2a6f
10 touches
10 conflicts
0x13b3e772…6835
0x34b655…2a6f
10 touches
10 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
66 conflicts on slot 0x89eaf36ae4…6e4e48
Audit this contract →
← previous block·next block →recent activity