← previous blocknext block →recent activity
Analyzing
Block #102,103,897
27 transactions · 23 stateful · 2026-09-05 05:38:36 UTC
Parallelism
85/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,103,897 · 27 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w120w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a9e408e…3721
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
2 touches
0 conflicts
0x04bdf44c…90af
0x34b655…2a6f
2 touches
0 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
2 touches
0 conflicts
0x1166cd31…f9c8
0x34b655…2a6f
2 touches
0 conflicts
0x173b64af…6c43
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 0x6a9e408e97…fb3721
Audit this contract →
← previous block·next block →recent activity