← previous blocknext block →recent activity
Analyzing
Block #106,541,693
28 transactions · 25 stateful · 2026-09-20 19:03:21 UTC
Parallelism
86/100
Blocked
44%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,541,693 · 28 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
1w02w03w14w15w26w010w115w116w217w018w119w220w323w024w125w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbaf6ed88…c179
0x34b655…2a6f
8 touches
6 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
8 touches
6 conflicts
0xfd426e0d…be2b
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x5a76543e…c0cd
0xd32edf…ff58
5 touches
3 conflicts
0x9ba10aad…9bc5
0x34b655…2a6f
4 touches
1 conflict
0xad862891…5d02
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
6 conflicts on slot 0xbaf6ed88a9…dec179
Audit this contract →
← previous block·next block →recent activity