← previous blocknext block →recent activity
Analyzing
Block #104,870,447
14 transactions · 14 stateful · 2026-09-14 22:49:32 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,870,447 · 14 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
2w05w06w111w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81d64349…50fe
0x34b655…2a6f
6 touches
3 conflicts
0x0b0611f7…e63a
0x34b655…2a6f
6 touches
3 conflicts
0xc09c3422…3c8b
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x7c68d10b…8386
0x34b655…2a6f
4 touches
1 conflict
0x0414693e…1d48
0x34b655…2a6f
2 touches
0 conflicts
0x0cdc5ffb…5790
0x34b655…2a6f
2 touches
0 conflicts
0x1b23371e…5aff
0x34b655…2a6f
2 touches
0 conflicts
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 0x81d643498b…3050fe
Audit this contract →
← previous block·next block →recent activity