← previous blocknext block →recent activity
Analyzing
Block #101,302,029
15 transactions · 15 stateful · 2026-09-02 10:16:04 UTC
Parallelism
87/100
Blocked
7%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,302,029 · 15 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
12w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfebfd83…c3ed
0x8964d7…10f8
4 touches
1 conflict
0xdfebfd83…c3ee
0x8964d7…10f8
4 touches
1 conflict
0xdfebfd83…c3f1
0x8964d7…10f8
4 touches
1 conflict
0xdfebfd83…c3f2
0x8964d7…10f8
4 touches
1 conflict
0xdfebfd83…c3f4
0x8964d7…10f8
4 touches
1 conflict
0xebfe17d4…f4b0
0x8964d7…10f8
4 touches
1 conflict
0xebfe17d4…f4b1
0x8964d7…10f8
4 touches
1 conflict
0xebfe17d4…f4b3
0x8964d7…10f8
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 0xdfebfd8353…d8c3ed
Audit this contract →
← previous block·next block →recent activity