← previous blocknext block →recent activity
Analyzing
Block #102,816,107
25 transactions · 17 stateful · 2026-09-07 17:44:09 UTC
Parallelism
80/100
Blocked
24%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,816,107 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w021w122w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b4f173c…94e6
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7dd96c96…7335
0x34b655…2a6f
6 touches
3 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xa5b88ff0…d758
0x34b655…2a6f
4 touches
1 conflict
0x38d193c0…554e
0x34b655…2a6f
3 touches
1 conflict
0x213ee207…a151
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
6 conflicts on slot 0x9b4f173cee…8c94e6
Audit this contract →
← previous block·next block →recent activity