← previous blocknext block →recent activity
Analyzing
Block #102,178,221
18 transactions · 16 stateful · 2026-09-05 11:55:22 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,178,221 · 18 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
1w04w05w17w010w112w114w215w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0c7e023…2a08
0x34b655…2a6f
6 touches
3 conflicts
0x818e1296…f4d7
0x34b655…2a6f
6 touches
3 conflicts
0xa4e9800f…4ab0
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x11998eac…f9a5
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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 0xe0c7e02326…532a08
Audit this contract →
← previous block·next block →recent activity