← previous blocknext block →recent activity
Analyzing
Block #101,064,195
28 transactions · 25 stateful · 2026-09-01 14:19:16 UTC
Parallelism
89/100
Blocked
16%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,064,195 · 28 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
3w04w05w16w214w016w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68531239…e9a3
0x34b655…2a6f
6 touches
3 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
4 touches
1 conflict
0x5dfaf9c4…30e8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x42daad7f…630b
0xa6afd3…d132
4 touches
1 conflict
0xb26ff3de…9352
0xa6afd3…d132
4 touches
1 conflict
0x10d80fee…dbda
0x34ae4d…3fc5
2 touches
0 conflicts
0x40970e69…da50
0x34ae4d…3fc5
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 0x68531239f9…5ae9a3
Audit this contract →
← previous block·next block →recent activity