← previous blocknext block →recent activity
Analyzing
Block #101,798,097
15 transactions · 14 stateful · 2026-09-04 03:51:45 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,798,097 · 15 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
1w02w13w212w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7872fdf7…2d4a
0xd32edf…ff58
5 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x116e7d…d8f1
2 touches
0 conflicts
0x00000000…0001
0x116e7d…d8f1
2 touches
0 conflicts
0x00000000…0003
0x116e7d…d8f1
2 touches
0 conflicts
0x00000000…0017
0x116e7d…d8f1
2 touches
0 conflicts
0xab2f6eed…254a
0x188d58…ea8e
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity