← previous blocknext block →recent activity
Analyzing
Block #102,321,281
21 transactions · 16 stateful · 2026-09-06 00:00:09 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,321,281 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w07w19w114w215w118w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c67d31e…3dbe
0x34b655…2a6f
6 touches
3 conflicts
0xafe81a7b…bcbf
0x34b655…2a6f
6 touches
3 conflicts
0x4ffd0eb8…29a1
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0002
0x116e7d…d8f1
4 touches
1 conflict
0x00000000…0003
0x116e7d…d8f1
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb81
0x1b6862…e19c
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 0x3c67d31e03…f03dbe
Audit this contract →
← previous block·next block →recent activity