← previous blocknext block →recent activity
Analyzing
Block #106,954,728
16 transactions · 15 stateful · 2026-09-22 05:43:12 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,954,728 · 16 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
1w02w04w15w27w38w410w112w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf90a6af3…1429
0x34b655…2a6f
12 touches
15 conflicts
0x01ad5dd0…11a1
0x34b655…2a6f
10 touches
10 conflicts
0x70986451…c6bd
0x34b655…2a6f
8 touches
6 conflicts
0xa9988419…9f45
0x34b655…2a6f
6 touches
3 conflicts
0x3198ab59…af3b
0x851145…3f07
4 touches
1 conflict
0x38de667a…9370
0x34b655…2a6f
4 touches
1 conflict
0x65e0a5c4…1103
0x34b655…2a6f
4 touches
1 conflict
0xd1b40f29…9b9d
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 0xf90a6af3ee…071429
Audit this contract →
← previous block·next block →recent activity