← previous blocknext block →recent activity
Analyzing
Block #102,055,078
11 transactions · 11 stateful · 2026-09-05 01:30:55 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,055,078 · 11 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
1w06w07w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20b94f7c…2a9b
0x34b655…2a6f
6 touches
3 conflicts
0x2fdf282c…cd81
0x34b655…2a6f
4 touches
1 conflict
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0x939cdd56…00c8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
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
3 conflicts on slot 0x20b94f7c91…602a9b
Audit this contract →
← previous block·next block →recent activity