← previous blocknext block →recent activity
Analyzing
Block #101,974,486
16 transactions · 16 stateful · 2026-09-04 18:42:29 UTC
Parallelism
88/100
Blocked
6%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,974,486 · 16 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e33015d…b134
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0xb27d87d6…6bf8
0x34b655…2a6f
4 touches
1 conflict
0xc97fbc05…088f
0x34b655…2a6f
4 touches
1 conflict
0xffdc4ab0…9626
0x34b655…2a6f
4 touches
1 conflict
0x3b096cfe…41e7
0x34b655…2a6f
4 touches
1 conflict
0x259b9b63…3b8b
0x34b655…2a6f
2 touches
0 conflicts
0x2a3f40b6…e39c
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 0x8e33015d6f…01b134
Audit this contract →
← previous block·next block →recent activity