← previous blocknext block →recent activity
Analyzing
Block #102,430,772
16 transactions · 15 stateful · 2026-09-06 09:14:55 UTC
Parallelism
81/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,430,772 · 16 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
1w02w16w09w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a3a8966…e993
0x34b655…2a6f
4 touches
1 conflict
0x9ee824ec…5faa
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x8d4c0bb9…ccd3
0x34b655…2a6f
2 touches
0 conflicts
0xc4feec13…d1b9
0x34b655…2a6f
2 touches
0 conflicts
0xc5459102…54de
0x34b655…2a6f
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 0x6a3a89660f…5ce993
Audit this contract →
← previous block·next block →recent activity