← previous blocknext block →recent activity
Analyzing
Block #102,011,827
10 transactions · 10 stateful · 2026-09-04 21:51:57 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,011,827 · 10 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
2w06w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b0611f7…e63a
0x34b655…2a6f
4 touches
1 conflict
0x29bbfffb…ea4a
0x34b655…2a6f
4 touches
1 conflict
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0xc5cfc032…d3bd
0x34b655…2a6f
4 touches
1 conflict
0x1e2dd67a…eb60
0x34b655…2a6f
2 touches
0 conflicts
0x2d2ef87a…d023
0x34b655…2a6f
2 touches
0 conflicts
0x33f90f29…4e8c
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 0x0b0611f77e…54e63a
Audit this contract →
← previous block·next block →recent activity