← previous blocknext block →recent activity
Analyzing
Block #102,505,849
24 transactions · 21 stateful · 2026-09-06 15:35:31 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,505,849 · 24 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
1w04w05w17w111w012w113w214w318w019w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
8 touches
6 conflicts
0xc77be88a…6cdc
0x34b655…2a6f
6 touches
3 conflicts
0xebe42450…94ae
0xe52b14…7230
5 touches
3 conflicts
0x3b7dce3c…0531
0x34b655…2a6f
4 touches
1 conflict
0x48a9b35f…e5a3
0x34b655…2a6f
4 touches
1 conflict
0x4f986ebc…737a
0x34b655…2a6f
4 touches
1 conflict
0x5090d98c…e741
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
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: 0xe52b1424…bb7230
6 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity