← previous blocknext block →recent activity
Analyzing
Block #101,993,654
17 transactions · 15 stateful · 2026-09-04 20:19:47 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,993,654 · 17 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
1w02w13w24w05w16w211w312w416w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d616e7c…a6a1
0x34b655…2a6f
6 touches
3 conflicts
0x2aa7be4c…0f84
0x34b655…2a6f
6 touches
3 conflicts
0x5c7b5ec0…0764
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x7daf6443…fd36
0x34b655…2a6f
6 touches
3 conflicts
0xda09bbc9…b41b
0x34b655…2a6f
6 touches
3 conflicts
0xe0da07e4…ccf2
0x34b655…2a6f
6 touches
3 conflicts
0xe53bd661…5352
0x34b655…2a6f
6 touches
3 conflicts
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 0x8d616e7c6c…98a6a1
Audit this contract →
← previous block·next block →recent activity