← previous blocknext block →recent activity
Analyzing
Block #101,016,364
14 transactions · 13 stateful · 2026-09-01 10:18:36 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,016,364 · 14 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7462b8f2…6312
0x34b655…2a6f
4 touches
1 conflict
0xb482658a…e4f5
0x34b655…2a6f
4 touches
1 conflict
0x9513aafb…bb7f
0x34b655…2a6f
4 touches
1 conflict
0x27b6010e…e4aa
0x34b655…2a6f
2 touches
0 conflicts
0x2f4f4437…1d3e
0x34b655…2a6f
2 touches
0 conflicts
0x5e8223c2…c242
0x34b655…2a6f
2 touches
0 conflicts
0x68531239…e9a3
0x34b655…2a6f
2 touches
0 conflicts
0x6c3b70b7…b9a5
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 0x7462b8f2c2…8d6312
Audit this contract →
← previous block·next block →recent activity