← previous blocknext block →recent activity
Analyzing
Block #103,214,108
22 transactions · 18 stateful · 2026-09-09 03:09:11 UTC
Parallelism
86/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #103,214,108 · 22 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
1w02w04w05w17w111w012w113w215w116w220w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18cf84a6…09e4
0x34b655…2a6f
6 touches
3 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x2905ed39…1865
0x34b655…2a6f
4 touches
1 conflict
0x29a58269…011a
0x34b655…2a6f
4 touches
1 conflict
0x2d4b76b6…d903
0x34b655…2a6f
4 touches
1 conflict
0x34f8df0b…ad11
0x34b655…2a6f
4 touches
1 conflict
0x4b84a880…6abb
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
3 conflicts on slot 0x18cf84a64e…8b09e4
Audit this contract →
← previous block·next block →recent activity