← previous blocknext block →recent activity
Analyzing
Block #104,202,591
26 transactions · 21 stateful · 2026-09-12 14:24:37 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.85
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,202,591 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w112w013w116w117w218w321w422w523w024w125w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6060c428…7ea0
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x588380ee…0a5c
0x34b655…2a6f
6 touches
3 conflicts
0x27754bd4…96ae
0x34b655…2a6f
6 touches
3 conflicts
0xb42efa35…7741
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x13db5960…6704
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
15 conflicts on slot 0x6060c4289d…d67ea0
Audit this contract →
← previous block·next block →recent activity