← previous blocknext block →recent activity
Analyzing
Block #101,970,251
57 transactions · 56 stateful · 2026-09-04 18:21:01 UTC
Parallelism
91/100
Blocked
16%
Avg conflicts / tx
0.3
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,970,251 · 57 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
1w02w13w25w09w115w216w117w219w355w356w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e7d7499…e3b7
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x30c777f3…bacc
0x34b655…2a6f
6 touches
3 conflicts
0x839d77a9…9a51
0x34b655…2a6f
6 touches
3 conflicts
0x5f749304…d1c1
0x34b655…2a6f
4 touches
1 conflict
0x67c1f465…38b3
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
6 conflicts on slot 0x9e7d749945…e2e3b7
Audit this contract →
← previous block·next block →recent activity