← previous blocknext block →recent activity
Analyzing
Block #102,306,580
17 transactions · 16 stateful · 2026-09-05 22:45:41 UTC
Parallelism
76/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,306,580 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w011w112w213w315w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1cd91e2f…3a9f
0x34b655…2a6f
8 touches
6 conflicts
0xe108b282…58b3
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6b267bdf…b173
0x34b655…2a6f
4 touches
1 conflict
0x6ca0994e…02ef
0x34b655…2a6f
4 touches
1 conflict
0x7b67f6cf…0aab
0x34b655…2a6f
4 touches
1 conflict
0x850dd907…2612
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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
6 conflicts on slot 0x1cd91e2f42…d83a9f
Audit this contract →
← previous block·next block →recent activity