← previous blocknext block →recent activity
Analyzing
Block #101,970,922
8 transactions · 8 stateful · 2026-09-04 18:24:25 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,970,922 · 8 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
1w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00f6a8a7…0e6e
0x34b655…2a6f
4 touches
1 conflict
0x5164e654…7d48
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x0813f9b8…1030
0x34b655…2a6f
2 touches
0 conflicts
0x0bd3f941…48ff
0x34b655…2a6f
2 touches
0 conflicts
0x0fb20484…1982
0x34b655…2a6f
2 touches
0 conflicts
0x26c599c1…706c
0x34b655…2a6f
2 touches
0 conflicts
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 0x00f6a8a766…070e6e
Audit this contract →
← previous block·next block →recent activity