← previous blocknext block →recent activity
Analyzing
Block #102,171,931
22 transactions · 19 stateful · 2026-09-05 11:23:31 UTC
Parallelism
68/100
Blocked
32%
Avg conflicts / tx
0.77
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,171,931 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w114w217w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x045532dd…4b7d
0x34b655…2a6f
6 touches
3 conflicts
0x94dabb65…43a3
0x34b655…2a6f
6 touches
3 conflicts
0x5363946e…9f68
0x34b655…2a6f
5 touches
3 conflicts
0x492dfcee…984c
0x34b655…2a6f
4 touches
1 conflict
0x644aa203…be62
0x34b655…2a6f
4 touches
1 conflict
0x73ae20cb…19f1
0x34b655…2a6f
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
10 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity