← previous blocknext block →recent activity
Analyzing
Block #101,973,506
11 transactions · 9 stateful · 2026-09-04 18:37:31 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,973,506 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddd20e39…d524
0x34b655…2a6f
4 touches
1 conflict
0xe40a656b…a98c
0x34b655…2a6f
4 touches
1 conflict
0x0fb20484…1982
0x34b655…2a6f
4 touches
1 conflict
0x2b7caca8…860f
0x34b655…2a6f
4 touches
1 conflict
0x402f41c1…6afc
0x34b655…2a6f
4 touches
1 conflict
0xa920abe6…6f3e
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x2aa7be4c…0f84
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 0xddd20e3989…a2d524
Audit this contract →
← previous block·next block →recent activity