← previous blocknext block →recent activity
Analyzing
Block #106,934,882
22 transactions · 21 stateful · 2026-09-22 04:03:18 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.91
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,934,882 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w011w112w213w314w415w516w119w220w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6758e5b6…93ae
0x34b655…2a6f
12 touches
15 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
12 touches
15 conflicts
0x8d5fc820…1750
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x926b278e…7f1b
0x851145…3f07
4 touches
1 conflict
0x5fa94b32…fd4d
0x851145…3f07
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
15 conflicts on slot 0x6758e5b62b…1393ae
Audit this contract →
← previous block·next block →recent activity