← previous blocknext block →recent activity
Analyzing
Block #106,934,696
21 transactions · 20 stateful · 2026-09-22 04:02:22 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,934,696 · 21 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
1w02w17w08w19w210w311w412w513w617w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ca519d1…4f93
0x34b655…2a6f
14 touches
21 conflicts
0x8590b692…b267
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0xbd590df7…9891
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c4
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
21 conflicts on slot 0x7ca519d11a…264f93
Audit this contract →
← previous block·next block →recent activity