← previous blocknext block →recent activity
Analyzing
Block #102,475,284
18 transactions · 17 stateful · 2026-09-06 13:00:19 UTC
Parallelism
89/100
Blocked
12%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,475,284 · 18 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
1w04w05w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63aaf6d9…f95c
0x34b655…2a6f
4 touches
1 conflict
0x676f9f01…a8ac
0x34b655…2a6f
4 touches
1 conflict
0x7c88e9b0…3a4b
0x34b655…2a6f
4 touches
1 conflict
0xcee5dc56…a77d
0x34b655…2a6f
4 touches
1 conflict
0x0ffac39e…6d34
0x34b655…2a6f
2 touches
0 conflicts
0x15f5bd00…cc44
0x34b655…2a6f
2 touches
0 conflicts
0x1c305add…dc72
0x34b655…2a6f
2 touches
0 conflicts
0x1f4f6368…86ef
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 0x63aaf6d9a5…8af95c
Audit this contract →
← previous block·next block →recent activity