← previous blocknext block →recent activity
Analyzing
Block #101,069,518
15 transactions · 14 stateful · 2026-09-01 14:46:18 UTC
Parallelism
87/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,069,518 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w010w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x703249c2…e321
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x75a8edef…26de
0x34b655…2a6f
4 touches
1 conflict
0x921b83c5…d545
0x34b655…2a6f
4 touches
1 conflict
0x56833c19…9f66
0x34b655…2a6f
4 touches
1 conflict
0x408e66bb…3d6b
0x34b655…2a6f
2 touches
0 conflicts
0x451e482b…7e7d
0x34b655…2a6f
2 touches
0 conflicts
0x55192654…91fe
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
1 conflict on slot 0x703249c2b6…bce321
Audit this contract →
← previous block·next block →recent activity