← previous blocknext block →recent activity
Analyzing
Block #101,992,794
27 transactions · 22 stateful · 2026-09-04 20:15:25 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,992,794 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w010w111w113w219w220w321w422w224w025w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65903ef9…2567
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x5f251b96…6054
0x34b655…2a6f
4 touches
1 conflict
0x62d6e82b…a750
0x34b655…2a6f
4 touches
1 conflict
0x7f127ad0…2bd6
0x34b655…2a6f
4 touches
1 conflict
0x8918384e…c413
0x34b655…2a6f
4 touches
1 conflict
0xa29cba63…8030
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
10 conflicts on slot 0x65903ef9a0…7d2567
Audit this contract →
← previous block·next block →recent activity