← previous blocknext block →recent activity
Analyzing
Block #101,324,815
15 transactions · 15 stateful · 2026-09-02 12:10:43 UTC
Parallelism
60/100
Blocked
47%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,324,815 · 15 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
1w03w04w05w16w28w310w112w113w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x336486a4…20bd
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x4940258b…0b39
0x851145…3f07
4 touches
1 conflict
0x4730fe0c…8960
0x34b655…2a6f
4 touches
1 conflict
0x676b5eb4…0b33
0x34b655…2a6f
4 touches
1 conflict
0x97096d9a…e280
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity