← previous blocknext block →recent activity
Analyzing
Block #101,016,786
11 transactions · 11 stateful · 2026-09-01 10:20:43 UTC
Parallelism
73/100
Blocked
18%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,016,786 · 11 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
6w07w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a548af5…0eb0
0x34b655…2a6f
6 touches
3 conflicts
0xc30ed460…38a0
0x34b655…2a6f
4 touches
1 conflict
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x067c87f1…e98a
0x34b655…2a6f
2 touches
0 conflicts
0x17d75238…7d7c
0x34b655…2a6f
2 touches
0 conflicts
0x33944a91…32df
0x34b655…2a6f
2 touches
0 conflicts
0x5e8223c2…c242
0x34b655…2a6f
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 0x5a548af508…f00eb0
Audit this contract →
← previous block·next block →recent activity