← previous blocknext block →recent activity
Analyzing
Block #102,706,404
24 transactions · 23 stateful · 2026-09-07 08:29:02 UTC
Parallelism
92/100
Blocked
13%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,706,404 · 24 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
4w05w010w011w113w118w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x014e90b3…470f
0x34b655…2a6f
4 touches
1 conflict
0xa92c8763…6d7f
0x34b655…2a6f
4 touches
1 conflict
0xbd22d0fc…64fd
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9b18cd88…5e04
0x065c9d…c394
3 touches
1 conflict
0xf9866093…dce6
0x065c9d…c394
3 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 0x014e90b366…e0470f
Audit this contract →
← previous block·next block →recent activity