← previous blocknext block →recent activity
Analyzing
Block #102,019,125
10 transactions · 9 stateful · 2026-09-04 22:28:51 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,019,125 · 10 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
1w02w03w17w28w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xced4ddba…d164
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x142c3bab…9c23
0x34b655…2a6f
4 touches
1 conflict
0x18a01188…42f0
0x851145…3f07
4 touches
1 conflict
0x992d3412…2cc3
0x851145…3f07
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x7a12283f…b18a
0x34ae4d…3fc5
2 touches
0 conflicts
0x915c095e…c1e5
0x34ae4d…3fc5
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 0xced4ddba6a…19d164
Audit this contract →
← previous block·next block →recent activity