← previous blocknext block →recent activity
Analyzing
Block #102,527,402
23 transactions · 21 stateful · 2026-09-06 17:24:47 UTC
Parallelism
83/100
Blocked
52%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,527,402 · 23 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
1w02w13w14w05w19w010w111w213w214w216w317w018w120w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e0c66fe…796f
0x1e2721…7805
6 touches
3 conflicts
0x00000000…0002
0x1e2721…7805
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf60db55a…a155
0x34b655…2a6f
6 touches
3 conflicts
0x431fa96d…6ac0
0x754704…b603
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x256918f1…c4d0
0x34b655…2a6f
4 touches
1 conflict
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: 0x1e27219e…bf7805
3 conflicts on slot 0x0e0c66fe54…87796f
Audit this contract →
← previous block·next block →recent activity