← previous blocknext block →recent activity
Analyzing
Block #102,219,493
19 transactions · 18 stateful · 2026-09-05 15:24:23 UTC
Parallelism
74/100
Blocked
22%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,219,493 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w011w112w213w317w018w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cf50d44…961b
0x34b655…2a6f
6 touches
3 conflicts
0xe108b282…58b3
0x34b655…2a6f
6 touches
3 conflicts
0x5b50b454…614a
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xffc921ce…dc0d
0x34b655…2a6f
4 touches
1 conflict
0x338b2ba3…b173
0x34b655…2a6f
4 touches
1 conflict
0x4559d99a…3138
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 0x3cf50d44a0…1e961b
Audit this contract →
← previous block·next block →recent activity