← previous blocknext block →recent activity
Analyzing
Block #101,064,870
27 transactions · 22 stateful · 2026-09-01 14:22:41 UTC
Parallelism
74/100
Blocked
36%
Avg conflicts / tx
0.85
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,064,870 · 27 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w09w116w218w320w421w022w125w526w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x89ac61bf…9443
0x34b655…2a6f
8 touches
6 conflicts
0xe30b38d0…ccf6
0x34b655…2a6f
6 touches
3 conflicts
0x2827ae77…4368
0x34b655…2a6f
6 touches
3 conflicts
0x42daad7f…630b
0xa6afd3…d132
4 touches
1 conflict
0x3a7ae9b9…5017
0x065c9d…c394
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity