← previous blocknext block →recent activity
Analyzing
Block #101,674,241
21 transactions · 19 stateful · 2026-09-03 17:28:48 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,674,241 · 21 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
2w03w14w25w37w19w010w114w415w016w119w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0x32e1d03e…68a7
0x34b655…2a6f
6 touches
3 conflicts
0xfa805f95…72a4
0x34b655…2a6f
6 touches
3 conflicts
0xeb1b66a1…ce4e
0x34b655…2a6f
6 touches
3 conflicts
0x123a68b3…202a
0x34b655…2a6f
6 touches
3 conflicts
0x56e0d685…c960
0x34b655…2a6f
6 touches
3 conflicts
0x5f749304…d1c1
0x34b655…2a6f
6 touches
3 conflicts
0x65f011a5…bc6e
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity