← previous blocknext block →recent activity
Analyzing
Block #101,955,608
16 transactions · 16 stateful · 2026-09-04 17:06:50 UTC
Parallelism
88/100
Blocked
6%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,955,608 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w011w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf18803af…e7a5
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0bd3f941…48ff
0x34b655…2a6f
2 touches
0 conflicts
0x45082691…dff7
0x34b655…2a6f
2 touches
0 conflicts
0x463e1e6b…87b5
0x34b655…2a6f
2 touches
0 conflicts
0x4dc996fa…e091
0x34b655…2a6f
2 touches
0 conflicts
0x4f3cc09a…2804
0x34b655…2a6f
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
1 conflict on slot 0xf18803af9e…fae7a5
Audit this contract →
← previous block·next block →recent activity