← previous blocknext block →recent activity
Analyzing
Block #101,324,631
24 transactions · 19 stateful · 2026-09-02 12:09:48 UTC
Parallelism
75/100
Blocked
32%
Avg conflicts / tx
0.46
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,324,631 · 24 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
2w03w05w17w112w014w220w321w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x3f16fb99…2fcf
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x7151b1ad…4520
0x34b655…2a6f
4 touches
1 conflict
0x2d02f869…1f83
0x34b655…2a6f
4 touches
1 conflict
0x024b482b…16b0
0x34b655…2a6f
4 touches
1 conflict
0x4947d921…28dc
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity