← previous blocknext block →recent activity
Analyzing
Block #104,023,543
15 transactions · 13 stateful · 2026-09-11 23:14:12 UTC
Parallelism
73/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,023,543 · 15 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
3w04w16w07w18w09w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30908823…a62d
0x34b655…2a6f
6 touches
3 conflicts
0xbfa8d1a6…c43c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x10379e8d…3675
0x34b655…2a6f
4 touches
1 conflict
0x38bcfe5f…6c71
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x59f5bb3d…0bc5
0x34b655…2a6f
4 touches
1 conflict
0x7b42f6a7…f49c
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 0x3090882336…22a62d
Audit this contract →
← previous block·next block →recent activity