← previous blocknext block →recent activity
Analyzing
Block #102,095,490
19 transactions · 17 stateful · 2026-09-05 04:55:57 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,095,490 · 19 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
1w02w13w24w311w014w116w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6823c28e…594c
0x34b655…2a6f
8 touches
6 conflicts
0xffc921ce…dc0d
0x34b655…2a6f
8 touches
6 conflicts
0xaaf36ccb…f35c
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x7c216fca…20cb
0x34b655…2a6f
6 touches
3 conflicts
0x999c658d…b185
0x34b655…2a6f
6 touches
3 conflicts
0x29a58269…011a
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
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
6 conflicts on slot 0x6823c28eb2…d0594c
Audit this contract →
← previous block·next block →recent activity