← previous blocknext block →recent activity
Analyzing
Block #101,315,217
17 transactions · 16 stateful · 2026-09-02 11:22:26 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,315,217 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w19w111w012w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0145862…6fa9
0x8964d7…10f8
4 touches
1 conflict
0xb0145862…6fa2
0x8964d7…10f8
4 touches
1 conflict
0xb0145862…6fa3
0x8964d7…10f8
4 touches
1 conflict
0xb0145862…6fa6
0x8964d7…10f8
4 touches
1 conflict
0xb0145862…6fa7
0x8964d7…10f8
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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: 0x8964d7c9…5b10f8
1 conflict on slot 0xb0145862e0…4c6fa9
Audit this contract →
← previous block·next block →recent activity