← previous blocknext block →recent activity
Analyzing
Block #101,966,680
19 transactions · 14 stateful · 2026-09-04 18:02:57 UTC
Parallelism
74/100
Blocked
57%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,966,680 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w16w27w38w212w313w014w118w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0003
0xaa5de1…d330
6 touches
3 conflicts
0x00000000…0002
0xaa5de1…d330
6 touches
3 conflicts
0x00000000…0000
0xaa5de1…d330
6 touches
3 conflicts
0xa74cd79c…705a
0x405b63…7777
6 touches
3 conflicts
0xbcc1b459…f94f
0x3bd359…433a
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x22e0cc1d…ad0d
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity