← previous blocknext block →recent activity
Analyzing
Block #101,975,857
18 transactions · 15 stateful · 2026-09-04 18:49:25 UTC
Parallelism
78/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,975,857 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w18w29w317w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fb20484…1982
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x04d962b7…1cc0
0x34b655…2a6f
4 touches
1 conflict
0x28673658…a4ca
0x34b655…2a6f
4 touches
1 conflict
0x8e33015d…b134
0x34b655…2a6f
4 touches
1 conflict
0x56a919c4…ab49
0x01bff4…1071
2 touches
0 conflicts
0xb1a4d6b6…304f
0x01bff4…1071
2 touches
0 conflicts
0x703b861a…cbe3
0x188d58…ea8e
2 touches
0 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 0x0fb20484a9…3a1982
Audit this contract →
← previous block·next block →recent activity