← previous blocknext block →recent activity
Analyzing
Block #106,242,381
21 transactions · 18 stateful · 2026-09-19 17:56:59 UTC
Parallelism
86/100
Blocked
22%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,242,381 · 21 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
7w08w111w014w115w018w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6a9e408e…3721
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xab1964de…941c
0xd32edf…ff58
3 touches
1 conflict
0x0de7749d…5bef
0x34b655…2a6f
2 touches
0 conflicts
0x65abd747…8a77
0x34b655…2a6f
2 touches
0 conflicts
0x870d5c00…5178
0x34b655…2a6f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity