← previous blocknext block →recent activity
Analyzing
Block #102,059,537
14 transactions · 14 stateful · 2026-09-05 01:53:33 UTC
Parallelism
79/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,059,537 · 14 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
1w02w14w25w06w19w010w111w212w013w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x5eae0b10…5837
0x34b655…2a6f
4 touches
1 conflict
0x64275949…d698
0x34b655…2a6f
4 touches
1 conflict
0x6636a104…d595
0x34b655…2a6f
4 touches
1 conflict
0x953517cb…cdec
0x34b655…2a6f
4 touches
1 conflict
0x9816fc81…4f3c
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
3 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity