← previous blocknext block →recent activity
Analyzing
Block #101,491,829
30 transactions · 26 stateful · 2026-09-03 02:11:08 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,491,829 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w19w010w011w112w119w220w021w123w226w228w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x92bb4e9d…0f03
0x34b655…2a6f
6 touches
3 conflicts
0x28eed2ad…c4b2
0x34b655…2a6f
4 touches
1 conflict
0x28eed2ad…c4b3
0x34b655…2a6f
4 touches
1 conflict
0x4d7ac770…c8f4
0x34b655…2a6f
4 touches
1 conflict
0x58799a46…7030
0x34b655…2a6f
4 touches
1 conflict
0x641aed07…bcb9
0x34b655…2a6f
4 touches
1 conflict
0x656d38f7…5426
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity