← previous blocknext block →recent activity
Analyzing
Block #101,305,930
17 transactions · 17 stateful · 2026-09-02 10:35:42 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,305,930 · 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
1w02w14w05w19w010w012w113w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7626c84e…7942
0x8964d7…10f8
4 touches
1 conflict
0x7626c84e…793c
0x8964d7…10f8
4 touches
1 conflict
0x7626c84e…793f
0x8964d7…10f8
4 touches
1 conflict
0x7626c84e…7940
0x8964d7…10f8
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x43e3decb…be40
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: 0x8964d7c9…5b10f8
1 conflict on slot 0x7626c84e80…a87942
Audit this contract →
← previous block·next block →recent activity