← previous blocknext block →recent activity
Analyzing
Block #105,435,524
17 transactions · 17 stateful · 2026-09-16 22:13:35 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
1.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,435,524 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w18w110w011w112w213w314w415w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5dac821…b68b
0x34b655…2a6f
10 touches
10 conflicts
0xb711a0b3…8019
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xd16ffb3d…fe01
0x34b655…2a6f
6 touches
3 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
6 touches
3 conflicts
0x485d2778…aa61
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x482471ad…122f
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
10 conflicts on slot 0xb5dac82174…f7b68b
Audit this contract →
← previous block·next block →recent activity