← previous blocknext block →recent activity
Analyzing
Block #106,397,099
24 transactions · 23 stateful · 2026-09-20 06:55:35 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,397,099 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w28w011w115w216w217w318w321w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cd235da…5aed
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x161db613…d254
0x34b655…2a6f
4 touches
1 conflict
0x2341fff4…32e2
0x34b655…2a6f
4 touches
1 conflict
0x39600f26…de5c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x502b3ee1…7f7c
0x34b655…2a6f
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
3 conflicts on slot 0x3cd235dab7…cf5aed
Audit this contract →
← previous block·next block →recent activity