← previous blocknext block →recent activity
Analyzing
Block #101,799,223
16 transactions · 15 stateful · 2026-09-04 03:57:25 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,799,223 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c60af1d…b1f9
0x34b655…2a6f
4 touches
1 conflict
0xe7fa4f4d…a2e4
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x02372d42…1871
0x34b655…2a6f
2 touches
0 conflicts
0x11628e1f…5a2d
0x34b655…2a6f
2 touches
0 conflicts
0x168f64f6…b4cb
0x34b655…2a6f
2 touches
0 conflicts
0x2330bf8b…047b
0x34b655…2a6f
2 touches
0 conflicts
0x2e42c10e…ac60
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 0x0c60af1d80…1ab1f9
Audit this contract →
← previous block·next block →recent activity