← previous blocknext block →recent activity
Analyzing
Block #105,376,956
21 transactions · 21 stateful · 2026-09-16 17:18:41 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,376,956 · 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
1w02w16w27w311w013w414w516w619w120w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf5135e2…1381
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x41bbce99…e285
0x34b655…2a6f
6 touches
3 conflicts
0x57330c5d…9973
0x34b655…2a6f
6 touches
3 conflicts
0x62db337c…f4c9
0x34b655…2a6f
4 touches
1 conflict
0x6c9de369…2fb5
0x34b655…2a6f
4 touches
1 conflict
0xb637c5df…5f2f
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
6 conflicts on slot 0xdf5135e227…ed1381
Audit this contract →
← previous block·next block →recent activity