← previous blocknext block →recent activity
Analyzing
Block #102,017,110
14 transactions · 14 stateful · 2026-09-04 22:18:39 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,017,110 · 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
4w07w08w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafb22303…6db3
0x34b655…2a6f
4 touches
1 conflict
0xb6ca29c6…1e2e
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5e8
0x34b655…2a6f
4 touches
1 conflict
0x65903ef9…2567
0x34b655…2a6f
4 touches
1 conflict
0x0ec07cf7…c0c9
0x34b655…2a6f
2 touches
0 conflicts
0x492dfcee…984c
0x34b655…2a6f
2 touches
0 conflicts
0x5363946e…9f68
0x34b655…2a6f
2 touches
0 conflicts
0x53e08444…d671
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 0xafb22303eb…7c6db3
Audit this contract →
← previous block·next block →recent activity