← previous blocknext block →recent activity
Analyzing
Block #102,059,441
12 transactions · 12 stateful · 2026-09-05 01:53:04 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,059,441 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33b7fbba…64de
0x34b655…2a6f
6 touches
3 conflicts
0x5dd033b6…34b5
0x34b655…2a6f
6 touches
3 conflicts
0xf139b130…d132
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xa735de1d…29b0
0x34b655…2a6f
4 touches
1 conflict
0xadc848ee…5cb2
0x34b655…2a6f
4 touches
1 conflict
0xd4f6a526…ad10
0x34b655…2a6f
4 touches
1 conflict
0xe6875750…9542
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: Perpl
3 conflicts on slot 0x33b7fbba1a…5e64de
Audit this contract →
← previous block·next block →recent activity