← previous blocknext block →recent activity
Analyzing
Block #106,272,127
30 transactions · 21 stateful · 2026-09-19 20:26:40 UTC
Parallelism
77/100
Blocked
52%
Avg conflicts / tx
0.97
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,272,127 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w07w113w215w317w018w123w224w325w126w428w529w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65903ef9…2567
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x18cf3003…51d1
0x065c9d…c394
8 touches
6 conflicts
0xcc8faac2…c766
0x065c9d…c394
8 touches
6 conflicts
0x94dabb65…43a3
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x9a291a56…9a9c
0x34b655…2a6f
6 touches
3 conflicts
0x9f63b181…919d
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x65903ef9a0…7d2567
Audit this contract →
← previous block·next block →recent activity