← previous blocknext block →recent activity
Analyzing
Block #101,681,763
19 transactions · 17 stateful · 2026-09-03 18:06:38 UTC
Parallelism
58/100
Blocked
65%
Avg conflicts / tx
1.79
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,681,763 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w16w27w38w49w511w612w714w115w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x846f2172…fd54
0x0555e3…2b9c
4 touches
1 conflict
0x8e80434a…a96d
0x0555e3…2b9c
4 touches
1 conflict
0x00000000…0000
0x2d82ac…5fd8
4 touches
1 conflict
0x00000000…0001
0x2d82ac…5fd8
4 touches
1 conflict
0x0259425f…039f
0x2d82ac…5fd8
4 touches
1 conflict
0x0dd3bdfb…7537
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
28 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity