← previous blocknext block →recent activity
Analyzing
Block #102,006,785
17 transactions · 17 stateful · 2026-09-04 21:26:25 UTC
Parallelism
88/100
Blocked
12%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,006,785 · 17 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
2w09w014w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xced4ddba…d164
0x34b655…2a6f
4 touches
1 conflict
0x4f125e89…7ee0
0x34b655…2a6f
4 touches
1 conflict
0x0cb6cb27…b0a1
0x34b655…2a6f
2 touches
0 conflicts
0x240838f0…5b9e
0x34b655…2a6f
2 touches
0 conflicts
0x2479a2c3…35e2
0x34b655…2a6f
2 touches
0 conflicts
0x2a8cef28…fd69
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity