← previous blocknext block →recent activity
Analyzing
Block #106,534,259
11 transactions · 11 stateful · 2026-09-20 18:25:56 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,534,259 · 11 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
1w02w13w14w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61037d3e…1885
0x34b655…2a6f
4 touches
1 conflict
0x82fd45e4…0935
0x34b655…2a6f
4 touches
1 conflict
0x8a015e17…d644
0x34b655…2a6f
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
0x3af041d1…6f61
0x34b655…2a6f
4 touches
1 conflict
0xba1edffb…323e
0x34b655…2a6f
4 touches
1 conflict
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0xe283e878…7262
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
1 conflict on slot 0x61037d3ef6…771885
Audit this contract →
← previous block·next block →recent activity