← previous blocknext block →recent activity
Analyzing
Block #102,305,826
16 transactions · 15 stateful · 2026-09-05 22:41:50 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,305,826 · 16 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
6w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8590b692…b267
0x34b655…2a6f
4 touches
1 conflict
0xc5c24509…7332
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x14be574b…a3e7
0x34b655…2a6f
2 touches
0 conflicts
0x53f7214d…8ec6
0x34b655…2a6f
2 touches
0 conflicts
0x56a284d9…32e4
0x34b655…2a6f
2 touches
0 conflicts
0xb91a6f59…722c
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 0x8590b69238…6ab267
Audit this contract →
← previous block·next block →recent activity