← previous blocknext block →recent activity
Analyzing
Block #101,975,331
21 transactions · 19 stateful · 2026-09-04 18:46:46 UTC
Parallelism
81/100
Blocked
37%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,975,331 · 21 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
2w03w14w25w111w013w214w316w017w118w020w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x0fb20484…1982
0x34b655…2a6f
8 touches
6 conflicts
0x04d962b7…1cc0
0x34b655…2a6f
6 touches
3 conflicts
0x8e33015d…b134
0x34b655…2a6f
6 touches
3 conflicts
0x31268b0b…3f5b
0x34b655…2a6f
4 touches
1 conflict
0x3a02129f…9eaf
0x34b655…2a6f
4 touches
1 conflict
0x448fdf2a…fab4
0x34b655…2a6f
4 touches
1 conflict
0x56e0d685…c960
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity