← previous blocknext block →recent activity
Analyzing
Block #104,193,290
14 transactions · 14 stateful · 2026-09-12 13:37:17 UTC
Parallelism
57/100
Blocked
43%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,193,290 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w18w210w311w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xabb9f292…17a3
0x34b655…2a6f
10 touches
10 conflicts
0x2bea5ce8…3c07
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x1507536e…933f
0x34b655…2a6f
4 touches
1 conflict
0x9301a8d9…fdad
0x34b655…2a6f
4 touches
1 conflict
0x949fc5d9…55f3
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity