← previous blocknext block →recent activity
Analyzing
Block #105,600,280
14 transactions · 13 stateful · 2026-09-17 12:02:43 UTC
Parallelism
79/100
Blocked
46%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,600,280 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w17w18w09w210w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9af9157…5a6e
0x34b655…2a6f
4 touches
1 conflict
0xf0a8a215…8f23
0x851145…3f07
4 touches
1 conflict
0xd6265424…0d3a
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x98552cba…5e9a
0x065c9d…c394
4 touches
1 conflict
0xc137f51f…cd2e
0x851145…3f07
4 touches
1 conflict
0xd35bb5ac…3586
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
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
1 conflict on slot 0xa9af9157e5…cc5a6e
Audit this contract →
← previous block·next block →recent activity