← previous blocknext block →recent activity
Analyzing
Block #105,435,605
11 transactions · 9 stateful · 2026-09-16 22:13:59 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,435,605 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x688bb5c8…c2da
0x34b655…2a6f
4 touches
1 conflict
0x7c51d9aa…af39
0x34b655…2a6f
4 touches
1 conflict
0xf6deafb5…5c25
0x34b655…2a6f
4 touches
1 conflict
0xff458cd9…d55a
0x34b655…2a6f
4 touches
1 conflict
0x07938824…3ecf
0x34b655…2a6f
2 touches
0 conflicts
0x0ffac39e…6d34
0x34b655…2a6f
2 touches
0 conflicts
0x173b64af…6c43
0x34b655…2a6f
2 touches
0 conflicts
0x1d69cd40…3a60
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x688bb5c873…7bc2da
Audit this contract →
← previous block·next block →recent activity