← previous blocknext block →recent activity
Analyzing
Block #101,019,710
19 transactions · 16 stateful · 2026-09-01 10:35:26 UTC
Parallelism
84/100
Blocked
25%
Avg conflicts / tx
0.37
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,019,710 · 19 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
2w05w06w110w011w116w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40f0cbff…df7c
0x34b655…2a6f
6 touches
3 conflicts
0x77582823…fe8e
0x34b655…2a6f
6 touches
3 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
6 touches
3 conflicts
0xd854a9d1…54d6
0x34b655…2a6f
4 touches
1 conflict
0xdca71fea…cf39
0x34b655…2a6f
4 touches
1 conflict
0x90a021f0…f922
0x34b655…2a6f
4 touches
1 conflict
0xa6eaff5d…3a8e
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
3 conflicts on slot 0x40f0cbff72…3adf7c
Audit this contract →
← previous block·next block →recent activity