← previous blocknext block →recent activity
Analyzing
Block #102,013,315
13 transactions · 13 stateful · 2026-09-04 21:59:28 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,013,315 · 13 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
1w02w13w27w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59d2df30…aff2
0x34b655…2a6f
6 touches
3 conflicts
0x492dfcee…984c
0x34b655…2a6f
6 touches
3 conflicts
0x1f396cee…862f
0x34b655…2a6f
4 touches
1 conflict
0x477cb4f5…11b4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5363946e…9f68
0x34b655…2a6f
4 touches
1 conflict
0x53f65ff1…cde1
0x34b655…2a6f
4 touches
1 conflict
0x5f749304…d1c1
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
3 conflicts on slot 0x59d2df3068…cbaff2
Audit this contract →
← previous block·next block →recent activity