← previous blocknext block →recent activity
Analyzing
Block #106,950,974
19 transactions · 19 stateful · 2026-09-22 05:24:18 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.84
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,950,974 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w18w19w210w211w314w417w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81903225…63ef
0x34b655…2a6f
10 touches
10 conflicts
0x1d81790c…b9f7
0x34b655…2a6f
8 touches
6 conflicts
0x1f396cee…862f
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xdfac3ce0…6699
0x99c7a7…8bf0
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd1b40f29…9b9d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
10 conflicts on slot 0x81903225b0…5d63ef
Audit this contract →
← previous block·next block →recent activity