← previous blocknext block →recent activity
Analyzing
Block #101,802,569
8 transactions · 8 stateful · 2026-09-04 04:14:15 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,802,569 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w27w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b3a121c…f803
0x34b655…2a6f
4 touches
1 conflict
0x0eac7709…66c3
0x34b655…2a6f
4 touches
1 conflict
0x6324ccc9…14fd
0x34b655…2a6f
4 touches
1 conflict
0x641d9ac7…a97d
0x34b655…2a6f
4 touches
1 conflict
0x7fa80a35…9142
0x34b655…2a6f
4 touches
1 conflict
0xa9dce007…24f4
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
1 conflict on slot 0x0b3a121ca7…4cf803
Audit this contract →
← previous block·next block →recent activity