← previous blocknext block →recent activity
Analyzing
Block #101,660,096
28 transactions · 27 stateful · 2026-09-03 16:17:38 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.68
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,660,096 · 28 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
1w02w13w04w17w28w312w314w415w224w527w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x375b6201…9c1e
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9b4f173c…94e6
0x34b655…2a6f
6 touches
3 conflicts
0xb556cb60…3636
0x34b655…2a6f
6 touches
3 conflicts
0xbb7e6651…ff5e
0x34b655…2a6f
6 touches
3 conflicts
0xb037179f…5b22
0x34b655…2a6f
4 touches
2 conflicts
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 0x375b620113…4b9c1e
Audit this contract →
← previous block·next block →recent activity