← previous blocknext block →recent activity
Analyzing
Block #101,313,824
37 transactions · 27 stateful · 2026-09-02 11:15:25 UTC
Parallelism
84/100
Blocked
63%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,313,824 · 37 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w37w08w110w411w112w113w215w224w225w326w428w532w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x2528e717…2a22
0x34b655…2a6f
6 touches
3 conflicts
0x40970e69…da50
0x34ae4d…3fc5
4 touches
1 conflict
0x8cf3d245…1d0d
0x34ae4d…3fc5
4 touches
1 conflict
0xb05cd4f5…73d0
0x34ae4d…3fc5
4 touches
1 conflict
0xdb067026…9eb8
0x34ae4d…3fc5
4 touches
1 conflict
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
15 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity