← previous blocknext block →recent activity
Analyzing
Block #102,306,022
10 transactions · 10 stateful · 2026-09-05 22:42:50 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,306,022 · 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
3w06w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0x81fe62e5…182b
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xf229fb25…39a5
0x34b655…2a6f
4 touches
1 conflict
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0x06e40499…165e
0x34ae4d…3fc5
2 touches
0 conflicts
0x45f562b2…9294
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 0x5d1ac445db…e05233
Audit this contract →
← previous block·next block →recent activity