← previous blocknext block →recent activity
Analyzing
Block #101,674,106
22 transactions · 19 stateful · 2026-09-03 17:28:07 UTC
Parallelism
73/100
Blocked
53%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,674,106 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w18w013w214w118w319w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0xeb1b66a1…ce4e
0x34b655…2a6f
8 touches
6 conflicts
0xa735de1d…29b0
0x34b655…2a6f
8 touches
6 conflicts
0xb3e293fe…be2e
0x34b655…2a6f
8 touches
6 conflicts
0x56e0d685…c960
0x34b655…2a6f
8 touches
6 conflicts
0x4babcbd0…e24c
0x34b655…2a6f
8 touches
6 conflicts
0x65f011a5…bc6e
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity