← previous blocknext block →recent activity
Analyzing
Block #105,549,068
19 transactions · 19 stateful · 2026-09-17 07:44:57 UTC
Parallelism
89/100
Blocked
16%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,549,068 · 19 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
1w05w09w114w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c6a407c…2b73
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x13a77505…f7d4
0x34b655…2a6f
2 touches
0 conflicts
0x14821eac…1646
0x34b655…2a6f
2 touches
0 conflicts
0x173b64af…6c43
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 0x0c6a407c9d…052b73
Audit this contract →
← previous block·next block →recent activity