← previous blocknext block →recent activity
Analyzing
Block #106,252,535
18 transactions · 15 stateful · 2026-09-19 18:48:05 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,252,535 · 18 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
1w02w03w15w06w18w211w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ec22d4c…411b
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x69411fb3…e36d
0x34b655…2a6f
4 touches
1 conflict
0x77ed432f…fa04
0x065c9d…c394
2 touches
0 conflicts
0x95523e2a…4c01
0x065c9d…c394
2 touches
0 conflicts
0xdd684690…f012
0x065c9d…c394
2 touches
0 conflicts
0xedaf5be2…85b0
0x065c9d…c394
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
3 conflicts on slot 0x1ec22d4c4c…10411b
Audit this contract →
← previous block·next block →recent activity