← previous blocknext block →recent activity
Analyzing
Block #102,052,716
28 transactions · 23 stateful · 2026-09-05 01:18:57 UTC
Parallelism
79/100
Blocked
43%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,052,716 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w016w017w118w119w120w221w322w423w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1e064bb…e40b
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x502b3ee1…7f7c
0x34b655…2a6f
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x69d2053b…935a
0x34b655…2a6f
4 touches
1 conflict
0x711ceb8d…5202
0x34b655…2a6f
4 touches
1 conflict
0xa57a72ed…64c2
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 0xf1e064bb0b…22e40b
Audit this contract →
← previous block·next block →recent activity