← previous blocknext block →recent activity
Analyzing
Block #102,094,972
20 transactions · 17 stateful · 2026-09-05 04:53:18 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,094,972 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w08w29w310w412w013w115w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd008c6e3…ecd2
0x34b655…2a6f
6 touches
3 conflicts
0xb637bebe…4cf9
0x34b655…2a6f
6 touches
3 conflicts
0x62bb20db…431e
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x9e7d7dbc…733b
0x34b655…2a6f
4 touches
1 conflict
0xa5a233a4…fd0f
0x34b655…2a6f
4 touches
1 conflict
0xab3df58f…531b
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity